Broadcast receiver and method for launching broadcaster application based on URL in application signaling information

ABSTRACT

A method for executing an application in a broadcasting receiver according to an embodiment of the present invention comprises the steps of: receiving application signaling information including information on an application; parsing application URL information including a URL where a specific application can be acquired, from the application signaling information; receiving one or more application content items relating to an application identified by the application URL information; and storing the received application content items.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of PCT International Application No.PCT/KR2015/010649, filed on Oct. 8, 2015, which claims priority under 35U.S.C. 119(e) to U.S. Provisional Application No. 62/063,908, filed onOct. 14, 2014, all of which are hereby expressly incorporated byreference into the present application.

TECHNICAL FIELD

The present invention relates to a broadcast signal transmission device,a broadcast signal reception device, and broadcast transceiving methods

BACKGROUND ART

As analog broadcast signal transmission is terminated, varioustechnologies for transmitting and receiving a digital broadcast signalhave been developed. A digital broadcast signal is capable of containinga larger amount of video/audio data than an analog broadcast signal andfurther containing various types of additional data as well asvideo/audio data.

DISCLOSURE Technical Problem

That is, a digital broadcast system may provide a high definition (HD)image, multi-channel audio, and various additional services. However,for digital broadcast, network flexibility obtained by considering datatransmission efficiency for a large amount of data transmission,robustness of a transceiving network, and a mobile receiving apparatusneeds to be enhanced.

Technical Solution

To solve the aforementioned problems, a broadcast receiver according toan embodiment of the present invention includes: a signaling parser forreceiving application signaling information including information aboutapplications; an application manager for parsing application URLinformation including a URL of a position at which a specificapplication is acquired from the application signaling information; anapplication browser for receiving one or more application content itemsrelated to an application identified by the application URL information;and a storage for storing the received application content items.

The application browser may call application link information, and theapplication manager may parse the application link information fromsignaling information and control information in the application linkinformation to be stored in the storage.

The application link information may include URI information indicatinga URL stored as a link for an application and link metadata informationincluding metadata related to the link.

The ink metadata information may include @packagedApp information forindicating whether the application connected through the link is apackaged application or an application in the form of a widget.

The link metadata information may include @url information indicating aURL of an object for the application indicated by the link, @titleinformation indicating a title of the link displayed to a user, or aParam element having values for discriminating a plurality ofapplications provided by the same application provider.

The application manager may receive a command for execution of aspecific application from a user and deliver the link metadatainformation to the application browser, and the application browser mayload application content items included in the specific application fromthe storage using the link metadata information.

The application browser may receive the application content items innon-real time through a broadcast network or receive the applicationcontent items through a broadband network.

A method of executing an application in a broadcast receiver accordingto an embodiment of the present invention includes: receivingapplication signaling information including information aboutapplications; parsing application URL information including a URL of aposition at which a specific application is acquired from theapplication signaling information; receiving one or more applicationcontent items related to an application identified by the applicationURL information; and storing the received application content items.

The method may further include: calling application link information;and parsing the application link information from signaling informationand controlling information in the application link information to bestored in the storage.

The application link information may include URI information indicatinga URL stored as a link for an application and link metadata informationincluding metadata related to the link.

The link metadata information may include @packagedApp information forindicating whether the application connected through the link is apackaged application or an application in the form of a widget.

The link metadata information may include @url information indicating aURL of an object for the application indicated by the link, @titleinformation indicating a title of the link displayed to a user, or aParam element having values for discriminating a plurality ofapplications provided by the same application provider.

The method may further include: receiving a command for execution of aspecific application from a user; delivering the link metadatainformation to the application browser; and loading application contentitems included in the specific application from the storage using thelink metadata information.

The receiving of the one or more application content items may includereceiving the application content items in non-real time through abroadcast network or receiving the application content items through abroadband network.

Advantageous Effects

According to the present invention, various broadcast services may beprovided by processing data according to service properties andcontrolling quality of service (QoS) of each service or servicecomponent.

According to the present invention, transmission flexibility may beachieved by transmitting various broadcast services through the sameradio frequency (RF) signal bandwidth.

According to the present invention, data transmission efficiency andtransceiving robustness of a broadcast signal may be enhanced using amultiple-input multiple-output (MIMO) system.

According to the present invention, rapid service scan and serviceacquisition may be provided.

According to the present invention, location information on anassociated component may be provided.

According to the present invention, service layer signaling may beselectively parsed using filtering information.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention.

FIG. 2 illustrates a BICM block according to an embodiment of thepresent invention.

FIG. 3 illustrates an orthogonal frequency division multiplexing (OFDM)generation block according to an embodiment of the present invention.

FIG. 4 illustrates a hybrid broadcast reception device according to anembodiment of the present invention.

FIG. 5 is a block diagram illustrating a hybrid broadcast receiveraccording to an embodiment of the present invention.

FIG. 6 shows a protocol stack of a next generation hybrid broadcastsystem according to an embodiment of the present invention.

FIG. 7 illustrates a method of transmitting signaling data in a nextgeneration broadcast system according to an embodiment of the presentinvention.

FIG. 8 shows signaling data transmitted by a next generation broadcastsystem according to an embodiment of the present invention for rapidbroadcast service scan of a receiver.

FIG. 9 shows signaling data transmitted by a next generation broadcastsystem according to an embodiment of the present invention for rapidbroadcast service scan of a receiver.

FIG. 10 illustrates a method of signaling a location of service layersignaling through FIC as signaling for rapid service scan andacquisition to acquire service layer signaling from the correspondinglocation according to an embodiment of the present invention.

FIG. 11 shows signaling data transmitted by a next generation broadcastsystem according to an embodiment of the present invention for rapidbroadcast service scan of a receiver.

FIG. 12 illustrates a method of signaling a location of service layersignaling through FIC as signaling for rapid service scan andacquisition to acquire service layer signaling from the correspondinglocation according to another embodiment of the present invention.

FIG. 13 shows a description of a transmission session instance of a nextgeneration broadcast system according to an embodiment of the presentinvention.

FIG. 14 shows a SourceFlow element of a next generation broadcast systemaccording to an embodiment of the present invention.

FIG. 15 shows an EFDT of a next generation broadcast system according toan embodiment of the present invention.

FIG. 16 shows a method for transmitting an ISDT used by a nextgeneration broadcast system according to an embodiment of the presentinvention.

FIG. 17 shows a delivery structure of a signaling message of a nextgeneration broadcast system according to an embodiment of the presentinvention.

FIG. 18 shows a trigger according to a trigger syntax of an embodimentof the present invention.

FIG. 19 shows a syntax of application signaling information according toan embodiment of the present invention.

FIG. 20 shows a syntax of an event stream element included in an MPDaccording to an embodiment of the present invention.

FIG. 21 shows a syntax of an event element of an event stream elementincluded in the MPD according to an embodiment of the present invention.

FIG. 22 illustrates a syntax of an event message box for in-band eventsignaling according to an embodiment of the present invention.

FIG. 23 shows a matching relationship between a trigger property forsignaling an application signaling information position and MPD elementsand the event message box according to an embodiment of the presentinvention.

FIG. 24 shows a matching relationship between a trigger property forsignaling an application state and MPD elements and the even message boxaccording to an embodiment of the present invention.

FIG. 25 shows a matching relationship between a trigger property forsignaling an application operation and MPD elements and the eventmessage box according to an embodiment of the present invention.

FIG. 26 shows a matching relationship between a trigger property forsignaling media time and MPD elements and the even message box accordingto an embodiment of the present invention.

FIG. 27 shows definition of a value attribute for signaling all triggerproperties as one event according to an embodiment of the presentinvention.

FIG. 28 shows a matching relationship between an identifier attributeand a message attribute of an event element for signaling all triggerproperties as one event and an identifier field and a message data fieldof the event message box according to an embodiment of the presentinvention.

FIG. 29 shows a structure of a package of an MMT protocol according toan embodiment of the present invention.

FIG. 30 shows a structure of an MMTP packet and data types included inthe MMTP packet according to an embodiment of the present invention.

FIG. 31 shows a syntax of an MMTP payload header when the MMTP packetincludes a fragment of an MPU according to an embodiment of the presentinvention.

FIG. 32 shows synchronization of content with a trigger transmittedthrough an MPU according to an embodiment of the present invention.

FIG. 33 shows a syntax of an MMT signaling message according to anotherembodiment of the present invention.

FIG. 34 shows a relationship between a value of an identifieridentifying an MMT signaling message and data signaled by the MMTsignaling message according to another embodiment of the presentinvention.

FIG. 35 shows a syntax of a signaling message including applicationsignaling information according to another embodiment of the presentinvention.

FIG. 36 shows a syntax of an application signaling table includingapplication signaling information according to another embodiment of thepresent invention.

FIG. 37 shows a relationship between trigger type information includedin an application signaling table and trigger properties included intriggers according to another embodiment of the present invention.

FIG. 38 shows a relationship between a value of an identifieridentifying an MMT signaling message and data signaled by the MMTsignaling message according to another embodiment of the presentinvention.

FIG. 39 shows a syntax of an application signaling table that does notinclude trigger type information according to another embodiment of thepresent invention.

FIG. 40 shows a structure of an MMTP packet according to anotherembodiment of the present invention.

FIG. 41 shows a structure of an MMTP packet and a syntax of a headerextension field for application signaling information transmissionaccording to another embodiment of the present invention.

FIG. 42 shows part of a broadcast system according to an embodiment ofthe present invention.

FIG. 43 shows an example in which a storage is included in a broadcastsystem according to an embodiment of the present invention.

FIG. 44 shows operation of a service worker according to an embodimentof the present invention.

FIG. 45 shows operation of a service worker in an offline stateaccording to an embodiment of the present invention.

FIG. 46 shows an application program interface (API) and metadata usedfor a receiver to execute an application according to an embodiment ofthe present invention.

FIG. 47 shows a user interface (UI) with respect to an application or alink for an application according to an embodiment of the presentinvention.

FIG. 48 shows a process through which a receiver installs and executesan application in the form of a widget according to an embodiment of thepresent invention.

FIG. 49 shows a process through which a user executes an applicationupon installation of the application according to an embodiment of thepresent invention.

FIG. 50 is a flowchart illustrating a method of executing an applicationby a broadcast receiver according to an embodiment of the presentinvention.

BEST MODE

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.

Although most terms of elements in this specification have been selectedfrom general ones widely used in the art taking into considerationfunctions thereof in this specification, the terms may be changeddepending on the intention or convention of those skilled in the art orthe introduction of new technology. Some terms have been arbitrarilyselected by the applicant and their meanings are explained in thefollowing description as needed. Thus, the terms used in thisspecification should be construed based on the overall content of thisspecification together with the actual meanings of the terms rather thantheir simple names or meanings.

In the specification, “signaling” refers to transmission/reception ofservice information (SI) provided by broadcast systems, Internetbroadcast systems and/or broadcast/Internet convergence systems. Theservice information includes broadcast service information (e.g.,ATSC-SI and/or DVB-SI) provided by existing broadcast systems.

In the specification, a “broadcast signal” is a concept includingsignals and/or data provided through interactive broadcast such asInternet broadcast, broadband broadcast, communication broadcast, databroadcast and/or video on demand (VOD) in addition to terrestrialbroadcast, cable broadcast, satellite broadcast and/or mobile broadcast.

In the specification, a “PLP” refers to a specific unit carrying databelonging to a physical layer. Accordingly, “PLP” may be replaced by“data unit” or “data pipe” in the specification.

A hybrid broadcast service implemented through interoperation betweenbroadcast networks and the Internet may be considered as one of powerfulapplications to be used in DTV services. The hybrid broadcast servicetransmits enhancement data associated with broadcast audio/video (A/V)content transmitted through terrestrial broadcast networks or part ofthe broadcast A/V content in real time such that a user can enjoyvarious types of content.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, aUHDTV service, etc.

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention.

The apparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can includean input formatting block 1000, a BICM (Bit interleaved coding &modulation) block 1010, a frame building block 1020, an OFDM (OrthogonalFrequency Division Multiplexing) generation block 1030 and a signalinggeneration block 1040. A description will be given of the operation ofeach module of the apparatus for transmitting broadcast signals.

IP stream/packets and MPEG2-TS are the main input formats, other streamtypes are handled as General Streams. In addition to these data inputs,Management Information is input to control the scheduling and allocationof the corresponding bandwidth for each input stream. One or multiple TSstream(s), IP stream(s) and/or General Stream(s) inputs aresimultaneously allowed.

The input formatting block 1000 can demultiplex each input stream intoone or multiple data pipe(s), to each of which an independent coding andmodulation is applied. The data pipe (DP) is the basic unit forrobustness control, thereby affecting quality-of-service (QoS). One ormultiple service(s) or service component(s) can be carried by a singleDP. Details of operations of the input formatting block 1000 will bedescribed later.

The data pipe is a logical channel in the physical layer that carriesservice data or related metadata, which may carry one or multipleservice(s) or service component(s).

Also, the data pipe unit: a basic unit for allocating data cells to a DPin a frame.

In the BICM block 1010, parity data is added for error correction andthe encoded bit streams are mapped to complex-value constellationsymbols. The symbols are interleaved across a specific interleavingdepth that is used for the corresponding DP. For the advanced profile,MIMO encoding is performed in the BICM block 1010 and the additionaldata path is added at the output for MIMO transmission. Details ofoperations of the BICM block 1010 will be described later.

The Frame Building block 1020 can map the data cells of the input DPsinto the OFDM symbols within a frame. After mapping, the frequencyinterleaving is used for frequency-domain diversity, especially tocombat frequency-selective fading channels. Details of operations of theFrame Building block 1020 will be described later.

After inserting a preamble at the beginning of each frame, the OFDMGeneration block 1030 can apply conventional OFDM modulation having acyclic prefix as guard interval. For antenna space diversity, adistributed MISO scheme is applied across the transmitters. In addition,a Peak-to-Average Power Reduction (PAPR) scheme is performed in the timedomain. For flexible network planning, this proposal provides a set ofvarious FFT sizes, guard interval lengths and corresponding pilotpatterns. Details of operations of the OFDM Generation block 1030 willbe described later.

The Signaling Generation block 1040 can create physical layer signalinginformation used for the operation of each functional block. Thissignaling information is also transmitted so that the services ofinterest are properly recovered at the receiver side. Details ofoperations of the Signaling Generation block 1040 will be describedlater.

FIG. 2 illustrates a BICM block according to an embodiment of thepresent invention.

The BICM block illustrated in FIG. 2 corresponds to an embodiment of theBICM block 1010 described with reference to FIG. 1.

As described above, the apparatus for transmitting broadcast signals forfuture broadcast services according to an embodiment of the presentinvention can provide a terrestrial broadcast service, mobile broadcastservice, UHDTV service, etc.

Since QoS (quality of service) depends on characteristics of a serviceprovided by the apparatus for transmitting broadcast signals for futurebroadcast services according to an embodiment of the present invention,data corresponding to respective services needs to be processed throughdifferent schemes. Accordingly, the a BICM block according to anembodiment of the present invention can independently process DPs inputthereto by independently applying SISO, MISO and MIMO schemes to thedata pipes respectively corresponding to data paths. Consequently, theapparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can controlQoS for each service or service component transmitted through each DP.

(a) shows the BICM block shared by the base profile and the handheldprofile and (b) shows the BICM block of the advanced profile.

The BICM block shared by the base profile and the handheld profile andthe BICM block of the advanced profile can include plural processingblocks for processing each DP.

A description will be given of each processing block of the BICM blockfor the base profile and the handheld profile and the BICM block for theadvanced profile.

A processing block 5000 of the BICM block for the base profile and thehandheld profile can include a Data FEC encoder 5010, a bit interleaver5020, a constellation mapper 5030, an SSD (Signal Space Diversity)encoding block 5040 and a time interleaver 5050.

The Data FEC encoder 5010 can perform the FEC encoding on the input BBFto generate FECBLOCK procedure using outer coding (BCH), and innercoding (LDPC). The outer coding (BCH) is optional coding method. Detailsof operations of the Data FEC encoder 5010 will be described later.

The bit interleaver 5020 can interleave outputs of the Data FEC encoder5010 to achieve optimized performance with combination of the LDPC codesand modulation scheme while providing an efficiently implementablestructure. Details of operations of the bit interleaver 5020 will bedescribed later.

The constellation mapper 5030 can modulate each cell word from the bitinterleaver 5020 in the base and the handheld profiles, or cell wordfrom the Cell-word demultiplexer 5010-1 in the advanced profile usingeither QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) ornon-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024) to give apower-normalized constellation point, el. This constellation mapping isapplied only for DPs. Observe that QAM-16 and NUQs are square shaped,while NUCs have arbitrary shape. When each constellation is rotated byany multiple of 90 degrees, the rotated constellation exactly overlapswith its original one. This “rotation-sense” symmetric property makesthe capacities and the average powers of the real and imaginarycomponents equal to each other. Both NUQs and NUCs are definedspecifically for each code rate and the particular one used is signaledby the parameter DP_MOD filed in PLS2 data.

The time interleaver 5050 can operates at the DP level. The parametersof time interleaving (TI) may be set differently for each DP. Details ofoperations of the time interleaver 5050 will be described later.

A processing block 5000-1 of the BICM block for the advanced profile caninclude the Data FEC encoder, bit interleaver, constellation mapper, andtime interleaver.

However, the processing block 5000-1 is distinguished from theprocessing block 5000 further includes a cell-word demultiplexer 5010-1and a MIMO encoding block 5020-1.

Also, the operations of the Data FEC encoder, bit interleaver,constellation mapper, and time interleaver in the processing block5000-1 correspond to those of the Data FEC encoder 5010, bit interleaver5020, constellation mapper 5030, and time interleaver 5050 described andthus description thereof is omitted.

The cell-word demultiplexer 5010-1 is used for the DP of the advancedprofile to divide the single cell-word stream into dual cell-wordstreams for MIMO processing. Details of operations of the cell-worddemultiplexer 5010-1 will be described later.

The MIMO encoding block 5020-1 can processing the output of thecell-word demultiplexer 5010-1 using MIMO encoding scheme. The MIMOencoding scheme was optimized for broadcasting signal transmission. TheMIMO technology is a promising way to get a capacity increase but itdepends on channel characteristics. Especially for broadcasting, thestrong LOS component of the channel or a difference in the receivedsignal power between two antennas caused by different signal propagationcharacteristics makes it difficult to get capacity gain from MIMO. Theproposed MIMO encoding scheme overcomes this problem using arotation-based pre-coding and phase randomization of one of the MIMOoutput signals.

FIG. 3 illustrates an OFDM generation block according to an embodimentof the present invention.

The OFDM generation block modulates the OFDM carriers by the cellsproduced by the Frame Building block, inserts the pilots, and producesthe time domain signal for transmission. Also, this block subsequentlyinserts guard intervals, and applies PAPR (Peak-to-Average Power Radio)reduction processing to produce the final RF signal.

Referring to FIG. 3, the OFDM generation block can include a pilot andreserved tone insertion block 8000, a 2D-eSFN encoding block 8010, anIFFT (Inverse Quick Fourier Transform) block 8020, a PAPR reductionblock 8030, a guard interval insertion block 8040, a preamble insertionblock 8050, other system insertion block 8060 and a DAC block 8070.

The other system insertion block 8060 can multiplex signals of aplurality of broadcast transmission/reception systems in the time domainsuch that data of two or more different broadcast transmission/receptionsystems providing broadcast services can be simultaneously transmittedin the same RF signal bandwidth. In this case, the two or more differentbroadcast transmission/reception systems refer to systems providingdifferent broadcast services. The different broadcast services may referto a terrestrial broadcast service, mobile broadcast service, etc.

FIG. 4 illustrates a hybrid broadcast reception device according to anembodiment of the present invention. The hybrid broadcast system maytransmit a broadcast signal in conjunction with a terrestrial broadcastnetwork and an Internet network. The hybrid broadcast reception devicemay receive a broadcast signal through a terrestrial broadcast network(broadcast) and an Internet network (broadband). The hybrid broadcastreception device may include a physical layer module, a physical layerI/F module, a service/content acquisition controller, an Internet accesscontrol module, a signaling decoder, a service signaling manager, aservice guide manager, an App signaling manager, an alert signalmanager, an alert signal parser, a targeting signal parser, a streamingmedia engine, a non-real-time file processor, a component synchronizer,a targeting processor, an application processor, an A/V processor, adevice manager, a data sharing and communication unit, a redistributionmodule, a companion device and/or an external module.

The physical layer module(s) may receive and process broadcast-relatedsignals through a terrestrial broadcast channel, convert the same intoappropriate forms, and transmit the converted signals to the physicallayer I/F module.

The physical layer I/F module(s) may acquire IP datagrams from theinformation obtained from the physical layer module. In addition, thephysical layer I/F module may convert the acquired IP datagram or thelike into a specific frame (for example, RS frame, GSE).

The service/content acquisition controller may perform controloperations for acquiring services, content and signaling data associatedtherewith over a broadcast and/or broadband channel.

The Internet access control module(s) may control receiver operations toacquire services, content, and the like over a broadband channel.

The signaling decoder may decode the signaling information acquired overa broadcast channel or the like.

The service signaling manager may extract, parse, and manage signalinginformation related to service scan and services/content from the IPdatagram and the like.

The service guide manager may extract announcement information from IPdatagrams, manage an SG (Service Guide) database, and provide a serviceguide.

The App signaling manager may extract, parse, and manage signalinginformation related to application acquisition and the like from IPdatagrams and the like.

The alert signal parser may extract, parse, and manage alerting relatedsignaling information from IP datagrams and the like.

The targeting signal parser may extract, parse, and manage signalinginformation related to service/content personalization or targeting fromIP datagrams and the like. The targeting signal parser may also deliverthe parsed signaling information to the targeting processor.

The streaming media engine may extract and decode audio/video data forA/V streaming from IP datagrams and the like.

The non-real time file processor may extract, decode, and manage NRTdata and file type data such as applications from IP datagrams and thelike.

The component synchronizer may synchronize services and content such asstreaming audio/video data and NRT data.

The targeting processor may process operations related topersonalization of the service/content based on the targeting signalingdata received from the targeting signal parser.

The application processor (App processor) may processapplication-related information, the status of a downloaded applicationand display parameters.

The A/V processor may perform audio/video rendering related operationsbased on decoded audio and video data, application data, and the like.

The device manager may perform connection and data exchange with anexternal device. The device manager may also perform management ofexternal devices such as addition/deletion/update of operativelyconnectable external devices.

The data sharing and communication unit (Data Sharing & Comm.) mayprocess information related to data transmission and exchange betweenthe hybrid broadcast receiver and an external device.

Here, the data that may be transmitted and exchanged may be signaling,A/V data, and the like.

The redistribution module(s) may acquire related information about thenext generation broadcast service and content when the broadcastreceiver cannot directly receive the terrestrial broadcast signal. Theredistribution module may also support acquisition of broadcast servicesand content by the next generation broadcast system when the broadcastreceiver cannot directly receive the terrestrial broadcast signal.

The companion device(s) may be coupled to the broadcast receiver of thepresent invention to share audio, video, or signaling-containing data.The companion device may refer to an external device connected to thebroadcast receiver.

An external management module (External Management) may refer to amodule for providing broadcast service/content, for example, a nextgeneration broadcast service/content server. The external module mayrefer to an external device connected to the broadcast receiver.

FIG. 5 is a block diagram illustrating a hybrid broadcast receiveraccording to an embodiment of the present invention.

The hybrid broadcast receiver may receive the hybrid broadcast servicethrough operative connection of terrestrial broadcast and broadband inthe DTV service of the next generation broadcast system. The hybridbroadcast receiver may receive broadcast audio/video (AN) contenttransmitted through a terrestrial broadcast and receive part ofenhancement data or broadcast A/V content associated therewith in realtime through broadband. In this specification, the broadcast audio/video(A/V) content may be referred to as media content.

The hybrid broadcast receiver may include a physical layer controllerD55010, a tuner D55020, a physical frame parser D55030, a link layerframe parser D55040, an IP/UDP datagram filter D55050, an ATSC 3.0 DTV(Digital Television) Control Engine D55060, an ALC/LCT+ Client D55070, atiming control D55080, a signaling parser D55090, a DASH (DynamicAdaptive Streaming over HTTP) client D55100, an HTTP access clientD55110, an ISO BMFF parser D55120, and/or a media decoder D55130.

The physical layer controller D55010 may control operations of the tunerD55020, the physical frame parser D55030, and the like using radiofrequency (RF) information about a terrestrial broadcast channel to bereceived by the hybrid broadcast receiver.

The tuner D55020 may receive and process broadcast related signalsthrough a terrestrial broadcast channel and convert the same into anappropriate form. For example, the tuner D55020 may convert a receivedterrestrial broadcast signal into a physical frame.

The physical frame parser D55030 may parse the received physical frameand acquire a link layer frame through related processing.

The link layer parser D55040 may acquire link layer signaling from thelink layer frame or perform related operations to acquire an IP/UDPdatagram or an MPEG-2 TS. The link layer parser D55040 may output atleast one IP/UDP datagram or the like.

The IP/UDP datagram filter D55050 may filter a specific IP/UDP datagramfrom at least one received IP/UDP datagram or the like. That is, theIP/UDP datagram filter D55050 may selectively filter an IP/UDP datagramselected by the ATSC 3.0 DTV control engine D55060 among the at leastone IP/UDP datagram output from the link layer parser D55040. The IP/UDPdatagram filter D55050 may output an application layer transportprotocol packet such as ALC/LCT+.

The ATSC 3.0 DTV control engine D55060 may serve as an interface betweenmodules included in each hybrid broadcast receiver. The ATSC 3.0 DTVcontrol engine D55060 may also provide necessary parameters for eachmodule, thereby controlling the operation of each module. In the presentinvention, the ATSC 3.0 DTV control engine D55060 may deliver a mediapresentation description (MPD) and/or an MPD URL to the DASH clientD55100. In the present invention, the ATSC 3.0 digital televisioncontrol engine D55060 may also deliver a delivery mode and/or atransport session identifier (TSI) to the ALC/LCT+ client D55070. Here,TSI may represent the identifier of a session for transmitting atransport packet including a signaling message such as MPD or MPD URLrelated signaling, for example, the identifier of a FLUTE session or anALC/LCT+ session, which is an application layer transmission protocol.The TSI may correspond to the Asset id of MMT.

The ALC/LCT+ client D55070 may process application layer transportprotocol packets such as ALC/LCT+, and collect and process a pluralityof packets to create one or more ISO Base Media File Format (ISOBMFF)objects. The application layer transport protocol packets may includeALC/LCT packets, ALC/LCT+ packets, ROUTE packets, and/or MMTP packets.

The timing control D55080 may process a packet including system timeinformation to control the system clock.

The signaling parser D55090 may acquire and parse DTV broadcast servicerelated signaling, and generate and manage a channel map and the likebased on the parsed signaling. In the present invention, the signalingparser may parse the extended MPD or MPD related information from thesignaling information.

The DASH client D55100 may perform operations related to real-timestreaming or adaptive streaming. The DASH client D55100 may receive DASHcontent from the HTTP server through the HTTP access client D55110. TheDASH client D55100 may process the received DASH segment and output anISO Base Media File Format object. In the present invention, the DASHclient D55100 may deliver a Fully Qualified Representation ID or asegment URL to the ATSC 3.0 DTV control engine D55060. Here, the FullyQualified Representation ID may refer to an ID that combines, forexample, the MPD URL, period@id, and representation@id. The DASH clientD55100 may also receive the MPD or MPD URL from the ATSC 3.0 DTV controlengine D55060. The DASH client D55100 may receive a desired media streamor DASH segment from the HTTP server using the received MPD or MPD URL.In this specification, the DASH client D55100 may be referred to as aprocessor.

The HTTP access client D55110 may make a request for specificinformation to the HTTP server, and may receive and process a responsefrom the HTTP server. Here, the HTTP server may process the requestreceived from the HTTP access client and provide a response thereto.

The ISO BMFF parser D55120 may extract audio/video data from the ISOBase Media File Format object.

The media decoder D55130 may decode the received audio and/or video dataand perform processing to present the decoded audio/video data.

The hybrid broadcast receiver of the present invention is required toextend or modify the MPD in order to provide the hybrid broadcastservice through operative connection between the terrestrial broadcastnetwork and the broadband. The terrestrial broadcast system may transmitthe extended or modified MPD, and the hybrid broadcast receiver mayreceive the broadcast or broadband content using the extended ormodified MPD. That is, the hybrid broadcast receiver may receive theextended or modified MPD through terrestrial broadcasting and receivecontent via terrestrial broadcasting or broadband based on MPD. Thefollowing describes elements and attributes that should be additionallyincluded in the extended or modified MPD compared to the existing MPD.In the following description, the extended or modified MPD may bereferred to as an MPD.

The MPD may be extended or modified to represent ATSC 3.0 services. Anextended or modified MPD may additionally includeMPD@anchorPresentationTime, Common@presentable, Common.Targeting,Common.TargetDevice and/or Common associatedTo.

MPD@anchorPresentationTime may represent the presentation time anchor ofsegments included in the MPD, that is, a base time. Hereinafter,MPD@anchorPresentationTime may be used as an effective time of the MPD.MPD@anchorPresentationTime may represent the earliest playback point intime among the segments included in the MPD.

The MPD may further include common attributes and elements. The commonattributes and elements may be applied to the AdaptionSet,Representation, SubRepresentation, and the like in the MPD.Common@presentable may indicate that the media described by MPD is apresentable component.

Common.Targeting may indicate the targeting properties and/orpersonalization properties of the media described by the MPD.

Common.TargetDevice may represent a target device or target devices ofthe media described by the MPD.

Common associatedTo may represent an adaptationSet and/or representationassociated with the media described by the MPD.

In addition, the MPD@id, Period@id, and AdaptationSet@id included in theMPD may be required to specify the media content described by the MPD.In other words, the DASH client may specify the content to be receivedas MPD@id, Period@id, and AdaptationSet@id based on the MPD and deliverthe same to the ATSC 3.0 DTV control engine. The ATSC 3.0 DTV controlengine may receive the content and deliver the same to the DASH client.

FIG. 6 shows a protocol stack of a next generation hybrid broadcastsystem according to an embodiment of the present invention.

As shown in the figure, a next generation broadcast system supportingIP-based hybrid broadcasting may encapsulate audio or video data of abroadcast service in an ISO Base Media File Format (hereinafter referredto as ISO BMFF). Here, the encapsulation may be in the form of a DASHsegment or an MPU (Media Processing Unit) of MMT. In addition, the nextgeneration broadcast system may transmit encapsulated data over thebroadcast network and the Internet network equally or differentlyaccording to the properties of each transmission network. The nextgeneration broadcast system may also transmit the encapsulated datausing at least one of broadcast or broadband. In case of broadcastnetwork, the broadcast system may transmit data encapsulated in ISO BaseMedia File (ISO BMFF) through an application layer transport protocolpacket supporting real time object transmission. For example, thebroadcast system may encapsulate the data with Real-Time Object Deliveryover Unidirectional Transport (ROUTE) or MMTP transport packet. Then,the broadcast system may generate an IP/UDP datagram from theencapsulated data, and transmit the same through a broadcast signal.When broadband is used, the broadcast system may transmit theencapsulated data to the receiving side based on a streaming techniquesuch as DASH.

In addition, the broadcast system may transmit the signaling informationof the broadcast service in the following manner. In the case of abroadcast network using broadcasting, the broadcast system may transmitsignaling information through the physical layer of the next generationbroadcast transmission system and the broadcast network according to theattribute of the signaling. Here, the broadcast system may transmitsignaling information through a specific data pipe (DP) of a transportframe included in the broadcast signal. The broadcast signaling may beencapsulated in a bit stream or an IP/UDP datagram. When usingbroadband, the broadcast system may return signaling data in response tothe request of the receiver.

In addition, the broadcast system may transmit the ESG or NRT content ofthe broadcast service in the following manner. In the case of abroadcast network, the broadcast system may encapsulate ESG or NRTcontent in an application layer transport protocol packet, for example,Real-Time Object Delivery over Unidirectional Transport (ROUTE), MMTPtransport packet, or the like. Then, the broadcast system may generatean IP/UDP datagram from the encapsulated ESG or NRT content and transmitthe same through a broadcast signal. When using broadband, the broadcastsystem may return the ESG or NRT content in response to the request ofthe receiver.

The broadcast system may transmit broadcast service related informationthrough a separate channel, for example, a Quick Information Channel(FIC), in order to enable the receiver to quickly scan the broadcastservice and content within the frequency.

The broadcast system may transmit information for scan and acquiringbroadcast services in a transport frame. Herein, the area including theinformation for scan and acquisition of broadcast services may bereferred to as FIC. The receiver may acquire information on thebroadcast service generated and transmitted by one or more broadcaststations through the FIC, thereby making it possible to easily andquickly perform scan of the broadcast services available on thereceiver.

In addition, a specific DP included in the transport frame may operateas a base DP for quickly and robustly transmitting signaling of abroadcast service and content transmitted in the corresponding transportframe. Link layer signaling or IP datagrams may be encapsulated in aspecific type of generic packet and then transmitted through the DP.Here, the generic packet may include signaling data. Link (low) layersignaling may include signaling related to quick servicescan/acquisition, context information of IP header compression,emergency alert, and the like.

FIG. 7 illustrates a method of transmitting signaling data in a nextgeneration broadcast system according to an embodiment of the presentinvention. The signaling data of the next generation broadcast systemmay be transmitted as shown in the figure. In order to support quickservice/content scan and acquisition by the receiver, the nextgeneration broadcast transmission system may deliver signaling data fora broadcast service delivered by a corresponding physical layer framethrough a Fast Information Channel (FIC). In the present specification,FIC may mean information on a service list. If there is no separate FIC,the signaling data may be transmitted through the path along which thelink layer signaling is delivered. In other words, signaling informationincluding a service and information on components (audio, video, etc.)in the service may be encapsulated and transmitted in IP/UDP datagramsthrough one or more DPs in the physical layer frame. According to anembodiment, the signaling information on a service and servicecomponents may be encapsulated and transmitted in an application layertransport packet (e.g., ROUTE packet or MMTP packet).

The upper part of FIG. 7 shows an embodiment in which theabove-described signaling data is transmitted via FIC and one or moreDPs. Signaling data for supporting rapid service scan/acquisition may betransmitted through FIC, and signaling data including detailedinformation about services and the like may be encapsulated in an IPdatagram and transmitted through a specific DP. In the presentspecification, the signaling data including detailed information onservices and the like may be referred to as service layer signaling.

The middle part of FIG. 7 shows an embodiment in which theabove-described signaling data is transmitted through the FIC and one ormore DPs. Signaling data for supporting rapid service scan/acquisitionmay be transmitted through FIC, and signaling data including detailedinformation about services and the like may be encapsulated in an IPdatagram and transmitted through a specific DP. In addition, a portionof the signaling data, including information about a specific componentincluded in the service may be transmitted through one or more transportsessions in the application layer transmission protocol. For example, aportion of the signaling data may be delivered over one or moretransport sessions within a ROUTE session.

The lower part of FIG. 7 shows an embodiment in which theabove-described signaling data is transmitted through the FIC and one ormore DPs. Signaling data for supporting rapid service scan/acquisitionmay be transmitted through FIC, and signaling data containing detailedinformation about the service may be transmitted through one or moretransport sessions in the ROUTE session.

FIG. 8 shows signaling data transmitted by a next generation broadcastsystem according to an embodiment of the present invention for rapidbroadcast service scan of a receiver.

The present specification proposes signaling information used for a nextgeneration broadcast reception device to scan and acquire a broadcastservice.

In the next generation broadcast system, broadcast services and contentgenerated by one or more broadcast stations within a specific frequencymay be transmitted. The receiver may use the above-described signalinginformation to rapidly and easily scan broadcast stations existingwithin the frequency and the service/content of the correspondingbroadcast stations. This may be represented by syntax as shown in thefigure or may be represented in other formats such as XML.

Signaling information for rapid service scan and acquisition may bedelivered over a rapid information channel (FIC), which is a separatechannel in the physical layer transport frame. In addition, thesignaling information may be transmitted through a common DP, which maytransmit information that may be shared among the data pipes of thephysical layer. Also, In addition, the signaling information may betransmitted through a path along which the signaling of the link layeris transmitted. The above-described signaling information may beencapsulated in an IP datagram and transmitted through a specific DP.

The signaling information may be transmitted through a service signalingchannel through which service signaling is delivered, or a transportsession of the application layer.

The signaling information (FIC information) for rapid service scan andacquisition may include at least one of the following fields. Herein,the FIC information may be referred to as service acquisitioninformation. The FIC_protocol_version field may indicate the protocolversion of the FIC signaling information (version of the structure ofFIC). The TSID field may indicate an identifier of the overall broadcaststream.

The FIC_data_version field may indicate the data version of the FICinstance. The FIC_data_version field may be incremented if there is achange in the content of the FIC. The num_partitions field may representthe number of partitions in the broadcast stream. It is assumed thateach broadcast stream can be transmitted in one or more partitions inorder for the num_partitions field to be used. Each partition maycontain a plurality of DPs by one broadcaster.

Each partition may represent a portion of the broadcast stream used byone broadcaster. The partition_protocol_version field may indicate theversion of the partition structure described above. The base_DP_ID fieldmay indicate an identifier for the base DP of the partition. The base DPmay include a service signaling table. The service signaling table mayinclude a list of all services in the partition.

That is, the service signaling table may list the services to betransmitted. Default properties for each service may also be defined.The base DP may be a robust DP within the partition and may containother signaling tables for the partition. The base_DP_version field mayindicate version information indicating a change in data transmittedthrough the base DP. For example, in transmitting service signaling orthe like through the base DP, the base_DP_version field may beincremented by 1 when a change in service signaling occurs. Thenum_services field may indicate the number of at least one servicebelonging to the partition. The service_id field may indicate anidentifier for the service. The channel_number field may indicate thechannel number associated with the service. The service_category fieldmay indicate a category of the corresponding service and may indicate,for example, A/V, audio, ESG, CoD, or the like. Theshort_service_name_length field may indicate the length of the namerepresenting the service.

The short_Service_name field may indicate a name representing theservice. The service_status field may indicate the status of the serviceand may indicate an active or suspended, hidden or shown attributedepending on the value thereof.

The service_distribution field may have attributes similar to the“multi-ensemble” flag of the ATSC M/H document. For example, theservice_distribution field may indicate information about whether theservice is included in the partition, whether the service is partiallyincluded in the partition but is presentable with the partition, whetheranother partition is required for presentation, or whether anotherbroadcast stream is required for presentation.

The sp_indicator field is a service protection flag that may indicatewhether one or more components needed for the presentation areprotected.

FIG. 9 shows signaling data transmitted by a next generation broadcastsystem according to an embodiment of the present invention for rapidbroadcast service scan of a receiver. FIC information (serviceacquisition information) to support rapid broadcast service scan andservice/component acquisition may include information about anapplication layer transport session carrying service and component data.As shown in the figure, the FIC information may be expressed in binaryformat, but may be represented in other formats such as XML according toan embodiment. The FIC information may include the fields as shown inthe figure. Description of fields which have been explained is omitted.The contents described with reference to FIG. 8 can be applied to thepresent description within a compatible range. The partition_id fieldmay indicate the identifier of the partition.

The partition_protocol_version field may indicate the version of thepartition structure described above.

The num_services field may indicate the number of at least one componentbelonging to the partition.

The service_id field may indicate an identifier for the service. Theservice_data_version field may indicate a change in service loop data inthe FIC or a change in service signaling data associated with theservice.

The service_data_version field may be incremented by 1 each time achange occurs in the included service data. The receiver may use theservice_data_version field to detect a change in the service loop dataof the FIC or a change in the signaling associated with the service.

The channel_number field may indicate the channel number associated withthe service.

The service_category field may indicate a category of the correspondingservice and may indicate, for example, A/V, audio, ESG, CoD, or thelike. The short_service_name_length field may indicate the length of thename representing the service. The short_service_name field may indicatea name representing the service. The service_status field may indicatethe status of the service and may indicate an active or suspended,hidden or shown attribute depending on the value thereof. Theservice_distribution field may have attributes similar to the“multi-ensemble” flag of the ATSC M/H document. The IP_version_flagfield may indicate the format of the IP address that follows. If thevalue of the field is 0, it indicates that IPv4 format is used, and if1, it indicates that IPv6 address format is used. Thesource_IP_address_flag field may indicate whether source_IP_addr isincluded. If the value of this field is 1, it indicates thatsource_IP_addr exists. The num_transport_session field may indicate thenumber of transport sessions (for example, ROUTE or MMTP sessions) fortransmitting component data of the corresponding service in thebroadcast stream. The source_IP_addr field may indicate the source IPaddress of the IP datagram including the component data of thecorresponding service when the value of the source_IP_address_flag is 1.The dest_IP_addr field may indicate the destination IP address of the IPdatagram including the component data of the corresponding service. Thedest_UDP_port field may indicate the UDP port number of the UDP datagramthat contains the component data of the corresponding service. TheLSID_DP field may represent a data pipe identifier of the physical layercarrying signaling including detailed information about the transportsession. Here, the signaling including the detailed information aboutthe transport session may be, for example, an LCT session instancedescription including information on the detailed LCT transport sessionof each ROUTE session in the case of ROUTE.

The service_signaling_flag field may indicate whether the transportsession transmits service signaling. When the value ofservice_signaling_flag is 1, it may indicate that the data transmittedthrough the corresponding transport session (for example, ROUTE or MMTPsession) includes service signaling. The Transport session descriptorsfield may contain descriptors at the transport session level. Eachdescriptor is extensible, and each descriptor may include anum_descriptors field. Each descriptor may include as many descriptorloops as the value indicated by the num_descriptors field.

The transport session descriptors field may contain descriptors at thetransport session level. The service descriptors field may includeservice level descriptors. The Partition descriptors field may include apartition level descriptor, and one partition may indicate a part of abroadcast stream used by one broadcaster or the like. The FIC sessiondescriptors field may contain FIC level descriptors. According to anembodiment, each of the fields included in the FIC described above maybe included in a table other than the FIC and transmitted together witha broadcast signal.

FIG. 10 illustrates a method for transmitting FIC-based signalingaccording to an embodiment of the present invention.

The above-mentioned FIC-based signaling may be delivered as shown in thefigure.

The FIC-based signaling may be referred to as service acquisitioninformation or service acquisition signaling. As shown in the figure,the physical layer signaling may include a field for service acquisitioninformation. The field for the service acquisition information mayinform the receiver of whether the service acquisition information (FIC)is parsed. The receiver may parse the service acquisition informationand check whether the data of the service signaling is changed throughthe service_data_version information. When the service signaling data ischanged, the broadcast signal receiver may check the data pipeidentifier of the physical layer that carries signaling includingdetailed information on the transport session, using the LSID_DP field.The broadcast receiver may verify the details of the transport sessionby parsing the DP indicated by the corresponding DP identifier. That is,the signaling method of the next generation broadcast system includes aprocedure of signaling whether the physical layer signaling parses theservice acquisition information, and the service acquisition informationsignals the location of the detailed information about the transportsession to check the detailed information about the transport session.Here, the detailed information about the transport session may includean MPD transport table, an application signaling table, a transportsession descriptor (LSID), and/or a component mapping table (CMT).

FIG. 11 shows signaling data transmitted by a next generation broadcastsystem according to an embodiment of the present invention for rapidbroadcast service scan of a receiver. FIC information (serviceacquisition information) to support rapid broadcast service scan andservice/component acquisition may include information about anapplication layer transport session carrying service and component data.As shown in the figure, the FIC information may be expressed in binaryformat, but may be represented in other formats such as XML according toan embodiment. The FIC information may include the fields as shown inthe figure. Description of fields which have been explained is omitted.The contents described with reference to FIG. 8 or FIG. 9 can be appliedto the present description within a compatible range.

The service_signaling_flag field may indicate whether the transportsession transmits service signaling. If the value of theservice_signaling_flag value is 1, it may indicate that there is a DPincluding service signaling. The signaling_data_version field mayindicate a change in the associated service signaling data. Each timethe service signaling data changes, the field may be incremented by 1.The receiver may use the signaling_data_version field to detect changesin the signaling associated with the service.

The signaling_DP field may indicate the data pipe identifier of thephysical layer carrying the service signaling. The Transport sessiondescriptors field may contain descriptors at the transport sessionlevel. Each descriptor is extensible, and each descriptor may include anum_descriptors field. Each descriptor may include as many descriptorloops as the value indicated by the num_descriptors field.

The Transport session descriptors field may contain descriptors at thetransport session level. The service descriptors field may includeservice level descriptors. The Partition descriptors field may include apartition level descriptor, and one partition may indicate a part of abroadcast stream used by one broadcaster or the like. The FIC sessiondescriptors field may contain FIC level descriptors. According to anembodiment, each of the fields included in the FIC described above maybe included in a table other than the FIC and transmitted together witha broadcast signal.

FIG. 12 illustrates a method for transmitting FIC-based signalingaccording to another embodiment of the present invention. Theabove-mentioned FIC-based signaling may be delivered as shown in thefigure.

The FIC-based signaling may be referred to as service acquisitioninformation or service acquisition signaling. As shown in the figure,the physical layer signaling may include a field for service acquisitioninformation. The field for the service acquisition information mayinform the receiver of whether the service acquisition information (FIC)is parsed. The receiver parses the service acquisition information andmay check whether the data of the service signaling is changed throughthe service_data_version information. When the service signaling data ischanged, the broadcast signal receiver may acquire the LSID or LSIDTable including detailed information on the transport session using theLSID_DP field through the DP identified from the LSID_DP field. Inaddition, the receiver may recognize change of the signaling data usinginformation such as service_signaling_flag, signaling_data_version,signaling_DP, etc., and acquire the signaling data through the DPidentified from the signaling_DP.

That is, the signaling method of the next generation broadcast systemincludes a procedure of signaling whether the physical layer signalingparses the service acquisition information, and the service acquisitioninformation signals the location of the detailed information about thetransport session to check the detailed information about the transportsession. Here, the detailed information about the transport session mayinclude an MPD transport table, an application signaling table, atransport session descriptor (LSID), and/or a component mapping table(CMT), and each detail of the transmission session may be delivered bydifferent examples.

FIG. 13 shows a description of a transmission session instance of a nextgeneration broadcast system according to an embodiment of the presentinvention. When the application layer transmission method is Real-TimeObject Delivery over Unidirectional Transport (ROUTE), a ROUTE sessionmay include one or more Layered Coding Transport (LCT) sessions. Thedetails of one or more transport sessions may be signaled through atransport session instance description. The transport session instancedescriptor may be referred to as LCT Session Instance Description (LSID)if it is ROUTE. In particular, the transport session instancedescription may define what is delivered by each LCT transport sessionconstituting the ROUTE session. Each transport session may be uniquelyidentified by the Transport Session Identifier (TSI). The transportsession identifier may be included in the LCT header. The transportsession instance description may describe all transport sessions thatare transmitted through the session. For example, the LSID may describea mode LCT session carried by a ROUTE session. The transport sessioninstance description may be delivered through the same ROUTE session asthe transport sessions, or may be delivered through different ROUTEsessions or unicast.

When delivered in the same ROUTE session, the transport session instancedescription may be transmitted in the transport session with a specifiedtransport session identifier (TSI) 0. Other objects referenced in thetransport session instance description may also be delivered with TSI=0,but may have a TOI value different from the transport session instancedescription. Alternatively, it may be delivered in a separate sessionwith TSI≠0. The transport session instance description may be updatedusing at least one of the version number, validity information, andexpiration information. The transport session instance description maybe represented in a bitstream or the like in addition to the illustratedformat.

The transport session instance description may include a versionattribute, a validFrom attribute, an expiration attribute, and mayinclude TSI attributes and SourceFlow and RepairFlow information foreach transport session. The version attribute may indicate the versioninformation about the corresponding transport session instancedescription, and the version information may be incremented each timethe content is updated. The transfer session instance description withthe highest version number may indicate the most recent valid version.The validFrom attribute may indicate when the transfer session instancedescription begins to be valid. The validFrom attribute may not beincluded in the transport session instance description according to anembodiment. This indicates that the transport session instancedescription is valid immediately upon receiving the description. Theexpiration attribute may indicate when the transfer session instancedescription expires.

The expiration attribute may not be included in the transport sessioninstance description according to the embodiment. This indicates thatthe transport session instance description is continuously valid. If atransport session instance description with an expiration attribute isreceived, expiration may conform to the expiration attribute. The TSIattribute may indicate a transport session identifier, and theSourceFlow element provides information about the source flow to betransmitted to the TSI, the details of which will be described below.The RepairFlow element may provide information about the repair flowsent to the corresponding TSI.

FIG. 14 shows a SourceFlow element of a next generation broadcast systemaccording to an embodiment of the present invention.

The source flow element may include an EFDT element, an idRef attribute,a realtime attribute, a minBufferSize attribute, an ApplicationIdentifier element, and a PayloadFormat element. The EFDT element mayinclude detailed information of the file delivery data. An EFDT mayindicate an extended File Delivery Table (FDT) instance, described inmore detail below. The idRef attribute may indicate the identifier ofthe EFDT and may be represented as a URI by the corresponding transportsession. The realtime attribute may indicate that the corresponding LCTpackets include an extension header. The extension header may include atimestamp indicating the presentation time of the delivery object. TheminBufferSize attribute may define the maximum amount of data needed tobe stored in the receiver. The Application Identifier element mayprovide additional information that may be mapped to an applicationcarried by that transport session. For example, the Representation ID ofthe DASH content or the Adaptation Set parameter of the DASHrepresentation for selecting a transport session for rendering may beprovided as additional information. The PayloadFormat element may definethe payload format of a ROUTE packet carrying an object of the sourceflow. The PayloadFormat element may include a codePoint attribute, adeliveryObjectFormat attribute, a fragmentation attribute, adeliveryOrder attribute, a sourceFecPayloadID attribute, and/or aFECParameters element. The codePoint attribute may define the structureof the packet with the code point value used in the payload. This mayindicate the value of the CP field in the LCT header.

The deliveryObjectFormat attribute may indicate the payload format ofthe delivery object. The fragmentation attribute may definefragmentation rules when an object to be transmitted is divided into oneor more transport packets. The deliveryOrder attribute may indicate theorder of transmission of the content of each transport packet carryingone transport object. The sourceFecPayloadID attribute may define theformat of the source FEC payload identifier. The FECParameters elementmay define FEC parameters. This may include FEC encoding id and instanceid.

FIG. 15 shows an EFDT of a next generation broadcast system according toan embodiment of the present invention.

The EFDT may include detailed information of the file delivery data. TheEFDT may include an idRef attribute, a version attribute, amaxExpiresDelta attribute, a maxTransportSize attribute, and aFileTemplate element. The idRef attribute may indicate the identifier ofthe EFDT. The version attribute may indicate the version of the EFDTinstance descriptor. This attribute may be incremented by 1 when EFDT isupdated. It may indicate that the EFDT having the highest version numberamong the received EFDTs is the currently valid version. ThemaxExpiresDelta attribute may indicate the maximum expiry time of theobject after the first packet associated with the object is sent.

The maxTransportSize attribute may indicate the maximum transmissionsize of the object described by the EFDT. For the FileTemplate element,the file URL or file template of the body part may be specified.

The transport session instance descriptor (LSID) element may betransmitted by the Transport Session Instance Descriptor Table (LSIDTable) at the bottom of the figure. The LSID table may be transmitted bythe above-described signaling message, which may be divided into asignaling message header and a signaling message data part. Thesignaling message data part may include a transport session instancedescriptor (LSID) or a part thereof. The signaling message data mayinclude a Transport Session Instance Descriptor (LSID) Table and mayinclude the following fields. The Signaling_id field may indicateidentifier information indicating that the signaling table includes atransport session instance descriptor (LSID). The protocol_version fieldmay indicate a protocol version of the signaling, such as a signalingsyntax that includes a transport session instance descriptor (LSID). TheSignaling_version field may indicate a change in signaling data,including a transport session instance descriptor (LSID). In addition,the transport session instance descriptor table may further include thecontent of the LSID element described above.

FIG. 16 shows a method for transmitting an ISDT used by a nextgeneration broadcast system according to an embodiment of the presentinvention.

The next generation broadcast system may transmit signaling informationfor the initialization segment of the DASH Representation associatedwith the component in the broadcast service by transmitting theInitialization Segment Delivery Table (ISDT). A signaling message forthe initialization segment of a DASH Representation associated with acomponent in a broadcast service may include a header and data. Thesignaling message header may conform to the above-described format, andthe signaling message data may include initialization segment deliveryinformation or a part thereof.

The initialization segment delivery information may include thefollowing information.

The Signaling_id information may identify the initialization segment ora signaling message including path information. The protocol_versioninformation may indicate the protocol version of the initializationsegment delivery table, such as the syntax of the correspondingsignaling message. The Sequence_number information may indicate theidentifier for an instance of the initialization segment delivery table.The Signaling_version information may indicate a change in the signalingdata of the initialization segment delivery table. The Service_idinformation may identify the service associated with the component.

The Mpd_id information may indicate an associated DASH MPD identifierassociated with the component.

The period_id information may indicate an associated DASH Periodidentifier associated with the component. The representation_idinformation may indicate a DASH representation identifier associatedwith the component. The initialization_segment_version information maybe version information indicating a change of the corresponding MPD orthe like. The Delivery_mode information may indicate information aboutwhether the initialization segment is included or is transmitted throughanother route. Initialization_segment_data( ) information may containthe initialization segment data itself. The initialization segment pathinformation may include information on a path for acquiring aninitialization segment, such as a URL for an initialization segment.Through the ISDT, the receiver may receive information about theInitialization segment of the DASH Representation associated with thecomponent.

FIG. 17 shows a delivery structure of a signaling message of a nextgeneration broadcast system according to an embodiment of the presentinvention.

The above signaling data may be communicated as shown in the figure ifit is sent based on an application layer transport, for example, ROUTE.That is, a part signaling may be transmitted through a fast informationchannel in order to support rapid service scan. And a part of thesignaling may be transmitted over a specific transport session and mayalso be delivered mixed with the component data.

The signaling information for supporting the rapid service scan andacquisition may be received on a channel separate from the transportsession. Here, the separate channel may mean a separate data pipe (DP).Further, detailed information about the service may be received througha separately designated transport session. The transport session mayhave a value of TSI=0. The information delivered through the transportsession designated herein may include an MPD delivery table, anapplication signaling table, a transport session instance descriptiontable, and/or a component mapping table. In addition, a part ofsignaling information may be delivered in the transport session alongwith the component data. For example, an initialization segment deliverytable may be delivered with the component data.

The lower part of the figure shows an embodiment of acquiring abroadcast service in a next generation broadcast network. The receivermay tune the broadcast and acquire and parse information for rapidservice scanning and acquisition when the service is selected. Thelocation of the service layer signaling or transport session instancedescription (e.g., LSID) is then determined from the information forrapid service scan and acquisition to acquire and parse the description.In addition, the receiver may identify the transport session includingthe signaling, from which it may acquire and parse the signaling table,and determine a desired component. Through this process, the desiredcomponent may be presented. That is, the broadcast service may beprovided to the user by acquiring information about the transportsession from the information for rapid service scan and acquisition,checking the position of the desired component from the informationabout the transport session, and reproducing the component.

Hybrid broadcast can provide services through applications.Specifically, a broadcaster may provide broadcast content relatedinformation through applications. For example, the broadcaster mayprovide an application through which products used by actors inbroadcast content can be purchased. For such an application, a broadcasttransmission device 10 may transmit application signaling informationfor signaling an application. The application signaling information mayinclude at least one of a trigger for triggering an application actionand triggering application information for signaling information about atriggered application. This will be described with reference to theattached drawings.

The triggering application information may include additionalinformation necessary to execute the application. Specifically, thetriggering application information may include application properties.Further, the triggering application information may include informationon a position at which a file included in the application can bedownloaded and received. In addition, the triggering applicationinformation may include information on a position at which an NRTcontent item used by the application can be received.

Furthermore, the triggering application information may signallife-cycle variation of the application. Specifically, the lift-cycle ofthe application may include at least one of preparing, executing,terminating and suspending. For example, execution of the applicationmay be prepared through the preparing state. In addition, theapplication may be executed in the preparing state. The application mayenter the terminating state by terminating execution thereof. Further,execution of the application may be suspended in the suspending state.

The triggering application information may include an action to beexecuted by the application. Specifically, the triggering applicationinformation may include data necessary to execute an application action.

The triggering application information may include media time.Specifically, the triggering application information may include mediatime of content synchronized with the application.

Specifically, the broadcast transmission device 10 may transmit atrigger for triggering an application action. Further, a broadcastreception device 100 may cause the application to execute a specificaction on the basis of the trigger. Specifically, the trigger may havethe format below.

The trigger may include a domain part indicating a registered Internetdomain name. In addition, the trigger may include a directory path partindicating a random character string for identifying a directory path ofthe domain name indicated by the domain part. Further, the trigger mayinclude a parameter part indicating a parameter for triggering theapplication. Specifically, the trigger may have the following format.

<domain name part>/<directory path>[?<parameter>]

Here, the domain name part and the directory path part may be mandatoryparts essentially included in the trigger. In addition, the parameterpart is an optional part optionally included in the trigger. Theparameter part may include at least one of an event ID for identifyingan event, an application ID for identifying a target application of thetrigger, and a timing value indicating a time when an event isperformed. Furthermore, the parameter part may include content mediatime. Moreover, the parameter part may include a content ID foridentifying content reproduced by the broadcast reception device 100. Inaddition, the parameter part may include spread information forspreading triggering application information request traffic of thebroadcast reception device 100. Further, the parameter set may includeversion information indicating a version of triggering applicationinformation related to the trigger.

Specifically, the parameter part may include at least one of thefollowing strings.

<media time>

<media time> and <spread>

<media time> and <version>

<media time> and <version> and <spread>

<event time>

<event time> and <spread>

<event time> and <version>

<event time> and <version> and <spread>

<event time> may include an event ID for identifying an event. Here, theevent may refer to execution of an action by the application accordingto the trigger. Here, the event ID may be designated by “e=”. Inaddition, the event ID may include two or three decimals following “e=”.Here, the decimals may be discriminated using a period (“.”). Further,<event time> may include an application ID for identifying theapplication that is a target of the trigger. Here, the application maybe called a triggered declarative object (TDO). The application ID maybe matched to an application ID of the triggering applicationinformation. Accordingly, the broadcast reception device 100 may acquireinformation about the application that is a target of the trigger fromthe triggering application information on the basis of the applicationID of the trigger. Here, the triggering application information may be aTDO parameter table (TPT) for signaling trigger information. Inaddition, the parameter part may include a data ID for identifying adata element used for the event. Further, the parameter part may includea timing value indicating a time when the event is performed. Here, thetiming value may be designated by “t=”. In a specific embodiment, thetiming value may be designated as a hexadecimal represented by one toeight characters following “t=”. When <event time> does not include thetiming value, the trigger may trigger the application to execute theevent at the trigger reception time.

<media time> may include media time of content. Specifically, <mediatime> may indicate a media time stamp of content synchronized with theapplication triggered by the trigger. Specifically, the media time maybe designated by “m=”. The media time may be designated as a hexadecimalrepresented by one to eight characters following “m=”. Further, <mediatime> may be denoted in milliseconds. In addition, <media time> mayindicate a content ID for identifying content currently reproduced bythe broadcast reception device 100. The content ID may be designated by“c=”. Specifically, when an application is executed according to adirect execution model, <media time> may include the content ID. In aspecific embodiment, the broadcast reception device 100 may receive atime base trigger delivering reference time for applicationsynchronization and extract the content ID from the time base trigger.Here, the broadcast reception device 100 may receive an interactiveservice for content currently reproduced thereby by transmitting thecontent ID to a server for the interactive service.

<version> may include version information indicating a version of thetriggering application information related to the trigger. Here, thetriggering application information may be a TPT. Specifically, theversion information may be designated by “v=”. Further, the versioninformation may be designated by a decimal represented by one to threecharacters following “v=”. The broadcast reception device 100 mayextract the version information from the trigger and acquire thetriggering application information on the basis of the versioninformation.

<spread> may include spread information that is a criterion forcalculation of a time for which the broadcast reception device 100 needsto wait to request that a server providing the application signalinginformation provide the triggering application information.Specifically, the broadcast reception device 100 may calculate a randomvalue on the basis of the time indicated by the spread information, waitfor the random value and then request the triggering applicationinformation. The spread information may be designated by “s=”.Specifically, the spread information may be designated by a decimalrepresented by one to three characters following “s=”. The broadcastreception device 100 can request the triggering application informationthrough the spread information to prevent traffic of the serverproviding the triggering application information from being concentratedon the trigger reception time.

<others> may include information other than the aforementionedparameters. The broadcast reception device 100 may ignore parametersthat are not recognizable.

A trigger including a media time of content may be called a time basetrigger. Specifically, the time base trigger may deliver a media timestamp of content reproduced by the broadcast reception device 100. Inaddition, the broadcast reception device 100 may generate a referencetime for synchronization between an application action and content onthe basis of the time base trigger.

A trigger including an event time may be called an activation triggerbecause the activation trigger designates a time when the correspondingevent is performed. The broadcast reception device 100 may perform atriggered operation on the basis of the event time of the trigger.Specifically, the broadcast reception device 100 may extract the eventtime from the trigger and perform an operation triggered at the eventtime.

In addition, the parameter part of the trigger may include not only atiming value indicating a time when an event starts to be performed butalso a timing value indicating a time when the event is ended. Further,when the broadcast reception device 100 receives the trigger after anevent start time and before an event end time, the broadcast receptiondevice 100 may perform the event triggered by the trigger. Specifically,the parameter part may include <event start time> and <event end time>.

<event start time> may include a timing value indicating a time when anevent starts to be performed. The timing value may be designated by“st=” following “e=” identifying the event.

<event end time> may include a timing value indicating a time when theevent is ended. The timing value may be designated by “et=” following“e=” identifying the event.

FIG. 18 shows a syntax according to the above-described trigger syntax.

In another specific embodiment, the trigger syntax may have a timed textformat displayed at a specific time. Specifically, timed text may beclosed captioning.

FIG. 19 shows a syntax of application signaling information according toan embodiment of the present invention.

As described above, the triggering application information may be calleda TPT. The triggering application information may signal applicationscorresponding to all program segments or partial program segmentsaccording to time. Here, a program segment indicates a time intervalincluded in a program.

The triggering application information may include protocol versioninformation indicating the protocol version of the triggeringapplication information. Specifically, the triggering applicationinformation may include major protocol version information indicatingmajor version information of a protocol and minor protocol versioninformation indicating additional version information of the protocol.Here, the major protocol version information may be a 3-bit integer. Thebroadcast reception device 100 may discard the triggering applicationinformation when the broadcast reception device 100 cannot support atleast one of the major protocol version information and the minorprotocol version information. The major protocol version information maybe referred to as MajorProtocolVersion. The minor protocol versioninformation may be referred to as MinorProtocolVersion. In a specificembodiment, the major protocol version information may be a 3-bitelement. The minor protocol version information may be a 4-bit element.

The triggering application information may include an ID for identifyingthe triggering application information. Specifically, the triggeringapplication information may be an ID identifying a program segment. In aspecific embodiment, an ID identifying a program segment may begenerated by combining a domain name and a program ID. For example, theID may be domain_name/program_id.

The triggering application information may include version informationfor indicating triggering application information update history. Thevalue of the version information may be changed whenever the triggeringapplication information is changed. The broadcast reception device 100may determine whether to extract detailed information included in thetriggering application information on the basis of the versioninformation. In a specific embodiment, the version information may bereferred to as tptVersion. In a specific embodiment, the versioninformation may be an 8-bit element.

The triggering application information may include expirationinformation indicating an expiration date and time of the triggeringapplication information. Specifically, the broadcast reception device100 may store the triggering application information and reuse thetriggering application information until the expiration date and timeindicated by the expiration information. In a specific embodiment, theexpiration information may be referred to as expirationDate. In aspecific embodiment, the expiration information may be a 16-bit element.

The triggering application information may include a service IDidentifying a service including an application. In a specificembodiment, the service ID may indicate an ID of a non-real-time (NRT)service defined in ATSC standards. In a specific embodiment, the serviceID may be referred to as serviceId. In a specific embodiment, theservice ID may be a 16-bit integer.

The triggering application information may include a base URL indicatinga base address of a URL included in application information. In aspecific embodiment, the base URL may be referred to as baseURL.

The triggering application information may include capabilityinformation indicating mandatory capabilities necessary for presentationof an application signaled by application information. The capabilityinformation may conform to definition of capabilities descriptor definedby ATSC standards. In a specific embodiment, the capability informationmay be referred to as Capabilities.

The triggering application information may include live triggerinformation that is generated in real time and transmitted through theInternet along with transmission of content. Specifically, the livetrigger information may include a URL of a server that transmits a livetrigger. In addition, the live trigger information may include a pollingperiod when the live trigger is transmitted according to polling. In aspecific embodiment, the live trigger information may be referred to asLiveTrigger. Further, the URL of the server that transmits the livetrigger may be referred to as URL. The polling period may be referred toas pollPeriod.

The triggering application information may include information about anapplication. Application information may include detailed information ofan application as a lower element. In a specific embodiment, theapplication information may be referred to as TDO.

The application information may include an application ID identifying anapplication. In a specific embodiment, the application ID may bereferred to as appID. Further, the application ID may be a 16-bitelement.

The application information may include application type informationindicating an application type. In a specific embodiment, when theapplication type information is “1”, the application type information isTDO. In a specific embodiment, the application type information may bereferred to as appType. In a specific embodiment, the application typeinformation may be a 16-bit element.

The application information may include application name informationindicating an application name. In a specific embodiment, theapplication name information may be referred to as appName.

The application information may include a global ID that globallyuniquely identifies an application. The global ID may be used toindicate the same application not only in the corresponding triggeringapplication information but also in other application information. In aspecific embodiment, the global ID may be referred to as globalID.

The application information may include application version informationcorresponding to version information indicating application updatehistory. In a specific embodiment, the application version informationmay be referred to as appVersion. In a specific embodiment, appVersionmay be an 8-bit element.

The application information may include cookie space informationindicating the size of a persistent storage space necessary for thebroadcast reception device 100 to execute an application. The cookiespace information may represent the size of a storage space necessary toexecute an application in kilobytes. In a specific embodiment, thecookie space information may be referred to as cookieSpace. In aspecific embodiment, the cookie space information may be an 8-bitelement.

The application information may include use frequency informationindicating the frequency of use of an application. The use frequencyinformation may indicate at least one of “only once”, “every hour”,“every day”, “every week” and “every month”. In a specific embodiment,the use frequency information may have a value in the range of 1 to 16.In a specific embodiment, the use frequency information may be referredto as frequencyOfUse.

The application information may include expiration informationindicating an expiration time and date of an application. In a specificembodiment, the expiration information may be referred to as expireDate.

The application information may include test application informationindicating an application for test broadcast. The broadcast receptiondevice 100 may ignore the application for test broadcast on the basis ofthe test application information. In a specific embodiment, the testapplication information may be referred to as testTDO. In a specificembodiment, the test application information may be a Boolean element.

The application information may include Internet availabilityinformation indicating that an application can be received through theInternet. In a specific embodiment, the Internet availabilityinformation may be referred to as availableInternet. In a specificembodiment, the Internet availability information may be a Booleanelement.

The application information may include broadcast availabilityinformation indicating that an application can be received through abroadcast network. In a specific embodiment, the broadcast availabilityinformation may be referred to as availableBroadcast. In a specificembodiment, the broadcast availability information may be a Booleanelement.

The application information may include URL information identifying afile corresponding to part of an application. In a specific embodiment,the application information may be referred to as URL.

The URL information may include entry information indicating whether thecorresponding file is an entry file. Specifically, the entry file refersto a file that needs to be executed first for execution of thecorresponding application.

The application information may include application boundary informationindicating the boundary of an application. In a specific embodiment, theapplication boundary information may be referred to asApplicationBoundary.

Furthermore, the application boundary information may include origin URLinformation necessary to add an application boundary. The origin URLinformation may be referred to as originURL.

The application information may include content item informationindicating information about a content item used by an application. Thecontent item information may include detailed information about thecontent item. In a specific embodiment, the content item information maybe referred to as contentItem.

The content item may include URL information identifying a filecorresponding to part of the corresponding content item. The URLinformation may be referred to as URL.

The URL information may include entry information indicating whether thecorresponding file is an entry content file. Specifically, an entry filerefers to a file that needs to be executed first for execution of thecorresponding content item. In a specific embodiment, the entryinformation may be referred to as entry.

The content item information may include update information indicatingwhether the corresponding content item can be updated. Specifically, theupdate information indicates whether the content item includes a fixedfile or is a real-time data feed. In a specific embodiment, the updateinformation may be referred to as updateAvail. The update informationmay be a Boolean element.

The content item information may include a polling period when whether afile included in the content item is updated through a polling method ischecked when the content item can be updated. Specifically, thebroadcast reception device 100 may check whether the content item isupdated on the basis of the polling period. Further, the polling periodmay be referred to as pollPeriod.

The content item information may include size information indicating thesize of the content item. In a specific embodiment, the size informationmay indicate a content item size in kilobytes. The size information maybe referred to as size.

The content item information may include Internet availabilityinformation indicating that the content item can be received through theInternet. In a specific embodiment, the Internet availabilityinformation may be referred to as availableInternet. In a specificembodiment, the Internet availability information may be a Booleanelement.

The content item information may include broadcast availabilityinformation indicating that the content item can be received through abroadcast network. In a specific embodiment, the broadcast availabilityinformation may be referred to as availableBroadcast. In a specificembodiment, the broadcast availability information may be a Booleanelement.

The application information may include event information indicatinginformation about an event of the application. In a specific embodiment,the event information may be referred to as Event.

The event information may include an event ID identifying the event.Specifically, the event ID can uniquely identify the event in thecorresponding application range. In a specific embodiment, the event IDmay be referred to as eventID. In a specific embodiment, the event IDmay be a 16-bit element.

The event information may include destination information indicating atarget device of the application. The destination information mayindicate that the application is only for a primary device that receivesbroadcast signals. The destination information may indicate that theapplication is only for one or more companion devices associated withthe primary device. The destination information may indicate that theapplication is for both the primary device and companion devices. In aspecific embodiment, the destination information may be referred to asdestination.

The event information may include diffusion information for diffusing atriggering application information request. Specifically, the broadcastreception device 100 may calculate a random value on the basis of thediffusion information, wait for the random value and then request theserver to provide triggering application information. Specifically, thebroadcast reception device 100 may wait for a time corresponding tomultiplication of the random value by 10 ms and then request the serverto provide the triggering application information. In a specificembodiment, the diffusion information may be referred to as diffusion.In a specific embodiment, the diffusion information may be an 8-bitelement.

The event information may include data information indicating dataassociated with the event. Each event may have a data element associatedtherewith. In a specific embodiment, the data information may bereferred to as Data.

The data information may include a data ID identifying data. The data IDmay be referred to as dataID. The data ID may be a 16-bit element.

In hybrid broadcast, media content can be transmitted using theMPEG-DASH protocol and the MMT protocol, as described above. When suchmedia content is transmitted, it is necessary to transmit a trigger fortriggering an application associated with the media content.Accordingly, a method of transmitting a trigger using the MPEG-DASHprotocol and the MMT protocol is required. This will be described belowwith reference to the attached drawings.

MPEG-DASH defines an event in order to deliver non-period information toa DASH client or an application. Further, MPEG-DASH defines anassociated event sequence as an event stream. Specifically, an MPEG-DASHevent may be used for delivery of timed information. Here, informationincluded in the MPEG-DASH event may be an event message. The MPEG-DASHevent may be delivered through an MPD. Further, the MPEG-DASH event maybe delivered through in-band of representation. The broadcasttransmission device 10 may transmit a trigger for triggering anapplication as an MPEG-DASH event.

Delivery of an MPEG-DASH event through an MPD will be described withreference to FIGS. 20 and 21.

FIG. 20 shows a syntax of an event stream element included in the MPDaccording to an embodiment of the present invention. FIG. 21 shows asyntax of an event element of the event stream element included in theMPD according to an embodiment of the present invention.

A presentation time of an event sequence of MPEG-DASH may be provided ata period level. Specifically, the period element of the MPD may includean event stream element indicating information about an event stream.The broadcast reception device 100 may finish an event when an end timeof a period including the event expires. Particularly, the broadcastreception device 100 may finish the event when the end time of theperiod including the event expires even when the event starts at aperiod boundary time.

A period element may include an event stream element containinginformation about an event stream. In a specific embodiment, the eventstream element may be referred to as Event Stream.

The event stream element may include a scheme ID element identifying ascheme of a message included in an event. In a specific embodiment, thescheme ID element may be referred to as schemeIDUri.

The event stream element may include a value element indicating a valuefor an event stream. In a specific embodiment, a value attribute may bereferred to as value.

The event stream element may include a time scale attribute indicating atime scale when an event included in an event stream is a timed event.In a specific embodiment, the time scale attribute may be referred to astimescale.

The event stream element may include an event element specifying eachevent and containing a message corresponding to the contents of thecorresponding event. In a specific embodiment, the event element may bereferred to as event.

The event element may include a presentation start time attributeindicating a presentation start time of an event. Specifically, thepresentation start time attribute may indicate a relative presentationstart time on the basis of a period start time. When the presentationstart time attribute is not present, the presentation start time mayhave a value of 0. In a specific embodiment, the presentation start timeattribute may be referred to as presentationTime.

The event element may include a presentation duration attributeindicating an event presentation duration. When the presentationduration attribute is not present, a presentation duration value may beunknown. In a specific embodiment, the presentation duration attributemay be referred to as duration.

The event element may include an ID attribute for identifying an event.Events which are related to the same content and have the same eventelement attribute value have the same ID element value.

Delivery of an MPEG-DASH event through an in-band stream will bedescribed with reference to FIG. 22.

FIG. 22 shows a syntax of an event message box for in-band eventsignaling according to an embodiment of the present invention.

The broadcast transmission device 10 may multiplex an event stream ofMPEG-DASH with a representation. Specifically, the broadcasttransmission device 10 may multiplex the event stream of MPEG-DASH aspart of segments with a representation.

The event stream of MPEG-DASH may be inserted into a selectedrepresentation. In a specific embodiment, the broadcast transmissiondevice 10 may insert the event stream into some representations includedin an adaptation set. In another specific embodiment, the broadcasttransmission device 10 may insert the event stream into allrepresentations included in the adaptation set.

An in-band event stream included in a representation may be representedby an in-band event stream element included in the adaption set or arepresentation level. In a specific embodiment, the in-band event streamelement may be referred to as InbandEventStream. In a specificembodiment, one representation may include a plurality of in-band eventstreams. Each in-band event stream may be represented by an additionalin-band event stream element.

The event message box “emsg” may provide signaling with respect to anormal event related to a media presentation time. Further, the eventmessage box may signal a specific action related to DASH operation. Whena media segment is encapsulated in ISO BMFF, the media segment mayinclude one or more event message boxes. Further, the event message boxmay be positioned before a moof box. “moof”.

The scheme of the event message box may be defined in the MPD. Further,the broadcast reception device 100 may ignore an event message boxhaving a scheme that is not defined in the MPD.

The event message box may include a scheme ID field for identifying thescheme of the event message box. In a specific embodiment, the scheme IDfield may be referred to as scheme_id_uri.

The event message box may include a value field indicating a value of anevent. The value of the value field may have a scheme and meaningdepending on the scheme identified by the scheme ID field. In a specificembodiment, the value field may be referred to as value.

The event message box may include a time scale field indicating a timescale related to the event message box. Specifically, the time scalefield may indicate time scales of a presentation start time delay fieldand a presentation duration field included in the event message box. Ina specific embodiment, the time scale field may be referred to astimescale.

The event message box may include the presentation start time delayfield that indicates a delay of an event presentation start time fromthe earliest presentation time. Specifically, the broadcast receptiondevice 10 may extract the earliest presentation time of a segment from asegment index box “sidx”. Here, the broadcast reception device 100 canacquire an event presentation start time by adding a time when thepresentation start time delay field appears to a segment presentationtime. In a specific embodiment, the presentation start time delay fieldmay be referred to as presentation_time_delta.

The event message box may include an event presentation duration fieldindicating an event presentation duration. When the event presentationduration field has a value of 0xffff, this indicates that the eventpresentation duration is unknown. In a specific embodiment, the eventpresentation duration field may be referred to as event_duration.

The event message box may include a message data field indicating a bodyof the message box. The message data field may have data depending onthe scheme of the message box.

Application signaling information can be transmitted by matching triggerproperties to an MPD element indicating an event stream of MPEG-DASH andan event message box indicating an in-band event stream. This will bedescribed with reference to FIGS. 23 to 28.

First of all, an MPEG-DASH event and an event described in thetriggering application information are explained to clearly discriminatethe terms. The MPEG-DASH event is additional information related to amedia time occasionally transmitted to a DASH client and an application.The event described in the triggering application information indicatesan event triggered by a trigger. Specifically, an event triggered by atrigger may represent execution of a specific action by an application.Further, an event triggered by a trigger may represent a state variationof an application. To discriminate an MPEG-DASH event from an eventtriggered by a trigger, the event triggered by the trigger is called atriggering event. Specifically, the triggering event can indicate anevent generated by a trigger.

FIG. 23 shows a matching relationship between a trigger property forsignaling the position of information about an application triggeredaccording to an embodiment of the present invention and MPD elements andan event message box.

The broadcast transmission device 10 may transmit the position oftriggering application information as an MPEG-DASH event. Here, the IDattribute included in the event element of the MPD may indicate the IDidentifying the triggering application information. Further, the messageof the event may represent the position of the triggering applicationinformation. The broadcast reception device 100 may receive thetriggering application information on the basis of the event element.Specifically, the broadcast reception device 100 may receive thetriggering application information by extracting the position of thetriggering application information from the message of the event.

In another specific embodiment, the ID field included in the eventmessage box may indicate the ID identifying the triggering applicationinformation. Further, the message data field included in the eventmessage box may indicate the position of the triggering applicationinformation. The broadcast reception device 100 may receive thetriggering application information on the basis of the event messagebox. Specifically, the broadcast reception device 100 may receive thetriggering application information by extracting the position of thetriggering application information from the message data field of theevent message box.

As described above, the triggering application information may be TPT.

FIG. 24 shows a matching relationship between a trigger property forsignaling an application status and MPD elements and an event messagebox according to an embodiment of the present invention.

The broadcast transmission device 10 may transmit an application statusas an MPEG-DASH event. Here, the presentation start time elementincluded in the event element of the MPD may indicate a start time of atriggering event. Further, the ID attribute included in the eventelement of the MPD may represent the ID identifying the triggeringapplication information. In addition, the message included in the eventelement may represent the application status. The broadcast receptiondevice 100 may change the application status on the basis of the eventelement. Specifically, the broadcast reception device 100 can change theapplication status by extracting the application status from the messageincluded in the event element. Specifically, the broadcast receptiondevice 100 can change the application status at a triggering event starttime by extracting the application status from the message included inthe event element and extracting the event start time from thepresentation start time element.

In another specific embodiment, the presentation start delay time fieldincluded in the event message box may indicate a triggering event starttime. Further, the ID field included in the event message box mayrepresent the ID identifying the triggering application information. Inaddition, the message data field included in the event message box mayrepresent the application status. The broadcast reception device 100 maychange the application status on the basis of the event message box.Specifically, the broadcast reception device 100 can change theapplication status by extracting the application status from the messagedata field of the event message box. In a specific embodiment, thebroadcast reception device 100 can change the application status at atriggering event start time by extracting the application status fromthe message data field of the event message box and extracting thetriggering event start time from the presentation start time delayfield.

The application status may represent at least one of preparing,execution, termination and suspending.

As described above, the triggering application information may be TPT.

FIG. 25 shows a matching relationship between a trigger property forsignaling application actions and MPD elements and an event message boxaccording to an embodiment of the present invention.

The broadcast transmission device 10 may transmit an application actionas an MPEG-DASH event. Here, the presentation start time elementincluded in the event element of the MPD may indicate a triggering eventstart time. Further, the presentation duration element included in theevent element of the MPD may represent a difference between thetriggering event start time and a triggering event end time. In anotherspecific embodiment, the presentation duration element included in theevent element of the MPD may indicate the triggering event end time.Further, the ID attribute included in the event element of the MPD mayindicate the ID identifying the triggering application information. Inaddition, the message included in the event element may represent anaction carried out by an application. Specifically, the message includedin the event element may include at least one of an application ID foridentifying a triggered application, an event ID for identifying atriggering event and a data ID for identifying data. Specifically, themessage included in the event element may be the aforementioned triggertype. Here, the message included in the event element may not includethe triggering event start time, triggering event end time and an IDidentifying a program segment, included in the aforementioned attribute.For example, the message included in the event element may bexbc.tv/e12?e=7.5. The broadcast reception device 100 may perform anapplication action on the basis of the event element. Specifically, thebroadcast reception device 100 may perform the application action byextracting the application action from the message included in the eventelement. Specifically, the broadcast reception device 100 may performthe application action at a triggering event start time by extractingthe application action from the message included in the event elementand extracting the triggering event start time from the presentationstart time element. In a specific embodiment, the broadcast receptiondevice 100 may perform the application action after the triggering eventstart time and before a triggering event end time by extracting theapplication action from the message included in the event element andextracting the triggering event start time from the presentation starttime element. The broadcast reception device 100 may ignore an MPEG-DASHevent message when the MPEG-DASH event message is received after thetriggering event end time.

In another specific embodiment, the presentation start delay time fieldincluded in the event message box may indicate a triggering event starttime. Further, the presentation duration field included in the eventmessage box of the MPD may represent a difference between the triggeringevent start time and a triggering event end time. In another specificembodiment, the presentation duration field included in the eventmessage box of the MPD may indicate the triggering event end time.Further, the ID field included in the event message box may indicate theID identifying the triggering application information. In addition, themessage data field included in the event message box may represent anaction carried by an application. Specifically, the message data fieldincluded in the event message box may include at least one of anapplication ID for identifying a triggered application, an event ID foridentifying a triggering event and a data ID for identifying data.Specifically, the message data field included in the event message boxmay be the aforementioned trigger type. Here, the message data fieldincluded in the event message box may not include the triggering eventstart time, triggering event end time and an ID identifying a programsegment, included in the aforementioned attribute. For example, themessage data field included in the event message box may bexbc.tv/e12?e=7.5. The broadcast reception device 100 may perform anapplication action on the basis of the event message box. Specifically,the broadcast reception device 100 may perform the application action byextracting the application action from the message data field of theevent message box. Specifically, the broadcast reception device 100 mayperform the application action at a triggering event start time byextracting the application action from the message data field of theevent message box and extracting the triggering event start time fromthe presentation start time delay field. In a specific embodiment, thebroadcast reception device 100 may perform the application action afterthe triggering event start time and before a triggering event end timeby extracting the application action from the message data field of theevent message box and extracting the triggering event start time fromthe presentation start time delay field. The broadcast reception device100 may ignore the event message box when the event message box isreceived after the triggering event end time.

FIG. 26 shows a matching relationship between a trigger property forsignaling a media time and MPD elements and an event message boxaccording to an embodiment of the present invention.

The broadcast transmission device 10 may transmit a media time ofcontent as an MPEG-DASH event. Here, the presentation start time elementincluded in the event element of the MPD may indicate the media time ofthe content. Here, the content may be content presented by the broadcastreception device 100. In addition, the ID attribute included in theevent element of the MPD may represent the ID identifying the triggeringapplication information. The broadcast reception device 100 may extractthe media time of the content on the basis of the event element.Further, the broadcast reception device 100 may generate a time linecorresponding to a basis of synchronization between a triggering eventand the content on the basis of the media time of the content.Specifically, the broadcast reception device 100 may generate the timeline corresponding to a basis of synchronization between the triggeringevent and the content by extracting the media time of the content fromthe presentation start time element included in the event element.

Furthermore, the presentation start time delay field included in theevent message box of the MPD may indicate a media time of content. Here,the content may be content presented by the broadcast reception device100. In addition, the ID attribute included in the event element of theMPD may represent the ID identifying the triggering applicationinformation.

The broadcast reception device 100 may extract the media time of thecontent on the basis of the event message box. Further, the broadcastreception device 100 may generate a time line corresponding to a basisof synchronization between a triggering event and the content on thebasis of the media time of the content. Here, the content may be contentpresented by the broadcast reception device 100. Specifically, thebroadcast reception device 100 may generate the time line correspondingto a basis of synchronization between the triggering event and thecontent by extracting the media time of the content from thepresentation start time delay field included in the event message box.

Accordingly, the broadcast reception device 100 can synchronize thecontent with the triggering event without extracting media timeinformation included in the content.

FIG. 27 shows definition of a value attribute for signaling all triggerproperties as one event according to an embodiment of the presentinvention.

To transmit a trigger as an MPEG-DASH event, the event element mayindicate the type of information signaled by the trigger. Specifically,the value attribute included in the event stream element may representthat a trigger included in the event message signals the position oftriggering application information. Here, the value of the valueattribute may be tpt. Further, the value attribute included in the eventstream element may represent that a trigger included in the eventmessage signals an application status. Here, the value of the valueattribute may be “status”. In addition, the value attribute included inthe event stream element may represent that a trigger included in theevent message signals an application action. Here, the value of thevalue attribute may be “action”. The value attribute included in theevent stream element may represent that a trigger included in the eventmessage signals a media time of content. Here, the value of the valueattribute may be “mediatime”. Further, the value attribute included inthe event stream element may represent that a trigger included in theevent message includes all information that can be included therein.Here, the value of the value attribute may be “trigger”.

In another specific embodiment, the value field included in the eventmessage box may represent that a trigger included in the data messagefield of the event message box signals the position of triggeringapplication information. Here, the value of the value field may be tpt.Further, the value field included in the event message box may representthat a trigger included in the data message field of the event messagebox signals an application status. Here, the value of the value fieldmay be “status”. In addition, the value field included in the eventmessage box may represent that a trigger included in the data messagefield of the event message box signals an application action. Here, thevalue of the value field may be “action”. The value field included inthe event message box may represent that a trigger included in the datamessage field of the event message box signals a media time of content.Here, the value of the value field may be “mediatime”. Further, thevalue field included in the event message box may represent that atrigger included in the data message field of the event message boxincludes all information that can be included therein. Here, the valueof the value field may be “trigger”. This will be described in detailbelow with reference to the attached drawings.

FIG. 28 shows a matching relationship between an ID attribute and amessage attribute of an event element for signaling all triggerproperties as one event and an ID field and a message data field of anevent message box according to an embodiment of the present invention.

As described above, one MPEG-DASH event can signal all properties thatcan be included in a trigger. Specifically, a message of an MPEG-DASHevent may include at least one of an ID identifying a triggeredapplication, an ID identifying a triggering event, an ID identifyingdata, a triggering event start time and a triggering event end time.

Here, the ID attribute of the event element may indicate an IDidentifying triggering application information. Further, the messageincluded in the event element may include a trigger. Specifically, themessage included in the event element may include a trigger in theaforementioned form. In addition, the message included in the eventelement may be a trigger in a timed text form.

Furthermore, the ID field of the event message box may indicate an IDidentifying triggering application information. Further, the messagedata field included in the event message box may include a trigger.Specifically, the message data field included in the event message boxmay include a trigger in the aforementioned form. In addition, themessage data field included in the event message box may include atrigger in a timed text form.

Accordingly, the broadcast transmission device 10 may transmit aplurality of trigger properties through one MPEG-DASH even message. Thebroadcast reception device 10 may acquire a plurality of triggerproperties through one MPEG-DASH event message.

Furthermore, a trigger may be signaled through the MMT protocol. Thiswill be described below with reference to the attached drawings.

FIG. 29 shows a structure of a package of the MMT protocol according toan embodiment of the present invention.

As described above, the MMT protocol can be used as a protocol fortransmitting media content in hybrid broadcast. Transmission of mediacontent through the MMT protocol will be described through a package, anasset, a media processing unit (MPU) and presentation information (PI).

The package is a logical transmission unit of content transmittedthrough the MMT protocol. Specifically, the package can include the PIand the asset.

The asset is an encoded media data unit included in the package. In aspecific embodiment, the asset may indicate an audio track included incontent. Further, the asset may represent a video track included incontent. The asset may indicate a captioning track included in content.The asset may include one or more MPUs.

The MPU is a media processing unit of content transmitted through theMMT protocol. Specifically, the MPU may include a plurality of accessunits. Further, the MPU may include data in a different format such asMPEG-4 AVC or MPEG-TS.

The PI is media content presentation information described above.Specifically, the PI may include at least one of spatial information andtemporal information necessary to consume the asset. In a specificembodiment, the PI may be composition information defined in ISO-IEC23008-1.

The broadcast transmission device 10 may transmit the package in an MMTPpacket corresponding to a transmission unit of the MMT protocol. Datatypes included in a payload of the MMTP packet will be described withreference to the following figure.

FIG. 30 shows a structure of an MMTP packet and data types included inthe MMTP packet according to an embodiment of the present invention.

The MMTP packet according to an embodiment of the present invention mayhave the structure shown in FIG. 30(a). Particularly, the MMTP packetcan represent the type of data included therein through a type field.

The MMTP packet may include a fragment of the MPU in the payload.Further, the MMTP packet may include a generic object indicating generaldata in the payload. Specifically, the generic object may be onecomplete MPU. Further, the generic object may be an object of adifferent type. The MMTP packet may include a signaling message in thepayload. Specifically, the MMTP packet may include one or more signalingmessages. Further, the MMTP packet may include a fragment of a signalingmessage. The signaling message may be a unit of signaling informationthat signals media content transmitted through the MMT protocol. TheMMTP packet may include one repair symbol. In a specific embodiment, thebroadcast transmission device 10 can transmit application signalinginformation through the MMTP packet including a fragment of the MPU.Specifically, the broadcast transmission device 10 can transmit atrigger through the MMTP packet including a fragment of the MPU.

FIG. 31 shows a syntax of an MMTP payload header when the MMTP packetincludes a fragment of the MPU according to an embodiment of the presentinvention.

When the MMTP packet includes a fragment of the MPU, the payload headerof the MMTP packet may include a length field indicating lengthinformation of the payload of the MMTP packet. In a specific embodiment,the length field may be referred to as “length”. In a specificembodiment, the length field is a 16-bit field.

When the MMTP packet includes a fragment of the MPU, the payload headerof the MMTP packet may include a type field indicating the type of theMPU included in the payload of the MMTP packet. Specifically, when theMMTP packet includes a fragment of the MPU, the payload of the MMTPpacket may include at least one of a media fragment unit, MPU metadataand movie fragment metadata. The MPU metadata may include ftyp, mmpu andmoov of ISO BMFF and other boxes included among ftyp, mmpu and moov. Themovie fragment metadata includes a moof box and a media data excludedmdat box. The media fragment unit may include at least one of a sampleof media data and a sub-sample. Here, the media data may be one of timedmedia data and non-timed media data. In a specific embodiment, the typefield may be referred to as FT. In a specific embodiment, the lengthfield may be a 4-bit field.

When the MMTP packet includes a fragment of the MPU, the payload headerof the MMTP packet may include a timed flag indicating whether thefragment of the MPU includes timed media. Specifically, when the valueof the timed flag is 1, the timed flag can indicate that the MPUfragment included in the MMTP packet includes timed media. In a specificembodiment, the timed flag may be referred to as T. In a specificembodiment, the timed flag may be 1-bit flag.

When the MMTP packet includes a fragment of the MPU, the payload headerof the MMTP packet may include a fragment indicator indicating fragmentinformation of a data unit included in the payload. The data unit mayrepresent the unit of data included in the payload of the MMTP packet.The payload of the MMTP packet may include one or more data units. In aspecific embodiment, the fragment indicator may be referred to as f_i.In a specific embodiment, the fragment indicator may be a 2-bit field.

When the MMTP packet includes a fragment of the MPU, the payload headerof the MMTP packet may include an aggregation flag indicating that thepayload includes one or more data units. In a specific embodiment, theaggregation flag may be referred to as A. In a specific embodiment, theaggregation flag may be a 1-bit flag.

When the MMTP packet includes a fragment of the MPU, the payload headerof the MMTP packet may include a fragment counter field indicating thenumber of fragments included in the same data unit included in thepayload. When the aggregation flag indicates that one or more data unitsare included in the payload, the value of the fragment counter field maybe 0. In a specific embodiment, the fragment counter field may bereferred to as frqg_counter. In a specific embodiment, the fragmentcounter field may be an 8-bit field.

When the MMTP packet includes a fragment of the MPU, the payload headerof the MMTP packet may include an MPU sequence field indicating a numberof a sequence including the MPU fragment. In a specific embodiment, theMPU sequence field may be referred to as MPU_sequence_number.

When the MMTP packet includes a fragment of the MPU, the payload headerof the MMTP packet may include a data unit length field indicating thelength of a data unit. Specifically, when the payload of the MMTP packetincludes one or more data units, the payload header of the MMTP packetmay include the data unit length field indicating a data unit length. Ina specific embodiment, the data unit length field may be referred to asDU_length. In a specific embodiment, the data unit length field may be a16-bit field.

When the MMTP packet includes a fragment of the MPU, the payload headerof the MMTP packet may include a data unit header field indicating aheader of a data unit. The data unit header field has a format dependingon the type of data included in the data unit. Specifically, the dataunit header field may have a format depending on the value of theaforementioned type field. Transmission of application signalinginformation using this payload header syntax will be described withreference to the following figure.

FIG. 32 shows synchronization of content with a trigger transmittedthrough an MPU according to an embodiment of the present invention.

The broadcast transmission device 10 may transmit application signalinginformation through a track of ISO BMFF by transmitting the same throughan MPU. Accordingly, the broadcast transmission device 10 can transmitthe application signaling information such that the applicationsignaling information is synchronized with content on a frame-by-framebasis. Specifically, the broadcast transmission device 10 can transmitthe application signaling information through the aforementioned payloadheader syntax of the MMTP packet such that the application signalinginformation can be synchronized with content on a frame-by-frame basis.In a specific embodiment, the broadcast transmission device 10 can setthe fragment type of the MPU to the media fragment unit, insert theapplication signaling information into the data unit payload andtransmit the application signaling information. Further, the broadcasttransmission device 10 may set the timed flag such that the timed flagindicates transmission of timed media. Specifically, the broadcasttransmission device 10 can set the timed flag such that the timed flagindicates transmission of timed media when the application signalinginformation needs to be transmitted at a specific time like a trigger.When application signaling information included in a data unit is atrigger, the trigger may have the aforementioned form. In anotherspecific embodiment, the trigger may have a timed text form. Further,the trigger may be XML. In addition, the trigger may include anapplication ID that identifies a triggered application. Further, thetrigger may include a triggering event ID that identifies a triggeringevent. The trigger may include an action indicating an action of atriggered application. Further, the trigger may include a data ID thatidentifies data necessary for a triggering event. In addition, thetrigger may include a triggering event start time. The trigger mayinclude a triggering event end time. As described above, the broadcastreception device 10 can perform an action after the triggering eventstart time and before the triggering event end time. Specifically, theapplication signaling information can be synchronized with a moviefragment presented in a decided sequence at a decided time through thetrigger. In a specific embodiment, the broadcast transmission device 10may set the triggering event start time and triggering event end time onthe basis of a media time in the movie fragment. Further, the broadcasttransmission device 10 may set the triggering event start time andtriggering event end time to relative time in the trigger. Otherwise,the broadcast transmission device 10 may set the triggering event starttime and triggering event end time to time based on wall-clock providedthrough out-of-band. For example, the broadcast transmission device 10can set the triggering event start time and triggering event end time totime based on wall-clock provided by CI. Further, the broadcasttransmission device 10 may set the triggering event start time andtriggering event end time to time based on wall-clock provided bytimestamp descriptor( ).

In the embodiment of FIG. 32, a first trigger (Trigger 1) issynchronized with a first movie fragment (Movie Fragment 1) and a secondtrigger (Trigger 2) is synchronized with a second movie fragment (MovieFragment 2). Specifically, the first trigger signals the position oftriggering application information according to the above-describedtrigger format and triggers a triggering event having a triggering eventID of 5 to be immediately executed for an application having anapplication ID of 7. The second trigger signals the position oftriggering application information according to the above-describedtrigger format and triggers a triggering event having a triggering eventID of 3 to be executed between 77ee to 80ee for an application having anapplication ID of 8.

The broadcast transmission device 10 may transmit an applicationsignaling message as a signaling message of the MMT protocol. This willbe described with reference to the following figure.

FIG. 33 shows a syntax of an MMT signaling message according to anotherembodiment of the present invention.

The MMT signaling message according to an embodiment of the presentinvention may include a message ID identifying the signaling message. Ina specific embodiment, the message ID may be referred to as message__id.In a specific embodiment, the message ID may be a 16-bit field.

In addition, the MMT signaling message may include version informationindicating update history of the signaling message. In a specificembodiment, the version information may be referred to as “version”. Ina specific embodiment, the version information may be an 8-bit field.

The signaling message may include length information indicating thelength of data included therein. The length information may be referredto as “length”. In a specific embodiment, the length information may bea 16-bit or 32-bit field.

The signaling message may include extension information indicating laterextension of the signaling message. The signaling message may includevarious types of information. This will be described with reference tothe following figure.

FIG. 34 shows a relationship between a value of an ID identifying an MMTsignaling message and data signaled by the MMT signaling messageaccording to another embodiment of the present invention.

Specifically, the signaling message may be a PA message indicatinginformation of all signaling tables. Here, the message ID may be 0x0000.The signaling message may be an MPI message including media contentpresentation information. Here, the message ID may be 0x0001 to 0x000F.The signaling message may be an MPT message including an MP tableindicating information of an asset included in a package. Here, themessage ID may be 0x0011 to 0x001F. Further, the signaling message maybe a CRI message including a CRI table indicating synchronizationinformation. Here, the message ID may be 0x0200. The signaling messagemay be a DCI message including a DCI table indicating device performancenecessary to consume a package. Here, message ID may be 0x0201. Further,the signaling message may be an AL_FEC message indicating FECinformation necessary to receive an asset. Here, the message ID may be0x0202. The signaling message may be an HRBM message indicating a memoryand end-to-end transmission delay necessary for the broadcast receptiondevice 100. Here, the message ID may be 0x0203. To transmit applicationsignaling information, the signaling message may be an applicationsignaling message including application signaling information other thanthe aforementioned messages. The broadcast reception device 100 canidentify the type of a message included in the signaling message throughthe above-described message ID. Here, the message ID may be 0x8000. Theform of the application signaling message will be described withreference to the following figure.

FIG. 35 shows a syntax of a signaling message including applicationsignaling information according to another embodiment of the presentinvention.

The application signaling message according to another embodiment of thepresent invention may include an application signaling table includingapplication signaling information in the signaling message. In aspecific embodiment, the signaling message may include a plurality ofapplication signaling tables.

The application signaling message may include table number informationindicating the number of application tables included in the applicationsignaling message. In a specific embodiment, the table numberinformation may be referred to as number_of_tables. The table numberinformation may be an 8-bit field.

The application signaling message may include table ID information thatidentifies an application table included therein. In a specificembodiment, the table ID information may be referred to as table_id. Thetable ID information may be an 8-bit field.

The application signaling message may include table version informationindicating signaling table update history. In a specific embodiment, thetable version information may be referred to as table_version. In aspecific embodiment, the table version information may be an 8-bitfield.

The application signaling message may include table length informationindicating the length of a signaling table. In a specific embodiment,the table length information may be referred to as table_length. In aspecific embodiment, the table length information may be an 8-bit field.A detailed syntax of the application signaling table will be describedwith reference to the following figure.

FIG. 36 shows a syntax of an application signaling table includingapplication signaling information according to another embodiment of thepresent invention.

The application signaling table according to another embodiment of thepresent invention may include an ID that identifies the applicationsignaling table. In a specific embodiment, the ID may be calledtable_id. The ID may be an 8-bit field.

The application signaling table may include version informationindicating application signaling table update history. In a specificembodiment, the version information may be called “version”. In aspecific embodiment, the version information may be an 8-bit field.

The application signaling table may include length informationindicating the length thereof. In a specific embodiment, the lengthinformation may be called “length”. In a specific embodiment, the lengthinformation may be a 16-bit field.

The application signaling table may include trigger type informationindicating the type of a trigger included therein. The signaling tablemay include various types of triggers. This will be described withreference to the following figure.

FIG. 37 shows a relationship between trigger type information includedin the application signaling table and trigger properties included intriggers according to another embodiment of the present invention.

A trigger included in the signaling table can signal the position oftriggering application information. Here, the trigger type informationmay be 1. Further, the trigger included in the signaling table cansignal the lifecycle of an application. Specifically, the triggerincluded in the signaling table can signal an application status. Here,the trigger type information may be 2. The trigger included in thesignaling table can signal an application action. Here, the trigger typeinformation may be 3. In addition, the trigger included in the signalingtable can signal a media time of content. Here, the trigger typeinformation may be 4. Further, the trigger included in the signalingtable can include all types of information that can be included in thetrigger. Here, the trigger type information may be 5. Description willbe given with reference to FIG. 36.

In a specific embodiment, the trigger type information may be calledtrigger_type. In a specific embodiment, the trigger type information maybe an 8-bit field.

Signaling information table may include text indicating a trigger.Specifically, the signaling information table may include characterinformation indicating characters included in the trigger. In a specificembodiment, the signaling information table may include multiple piecesof character information. In a specific embodiment, the characterinformation may be called URI_character. Further, the trigger may havethe aforementioned form. In a specific embodiment, the characterinformation may be an 8-bit field.

In the embodiment described with reference to FIGS. 36 and 37, triggertypes are represented through the trigger type information in theapplication signaling message table. In this case, the broadcastreception device 100 needs to parse the application signaling table torecognize a trigger type. Accordingly, the broadcast reception device100 cannot selectively receive only a necessary trigger. A method forsolving this problem will be described with reference to the followingfigure.

FIG. 38 shows a relationship between a value of an ID identifying an MMTsignaling message and data signaled by the MMT signaling messageaccording to another embodiment of the present invention.

The broadcast transmission device 10 can set the message ID foridentifying an application signaling message depending on the type of atrigger included in the application signaling message. Specifically, thebroadcast transmission device 10 can set the message ID depending onwhether the trigger is a trigger signaling the position of triggeringapplication information, a trigger signaling an application lifecycle, atrigger signaling an application action, a trigger signaling a contentmedia time or a trigger including all trigger information. Specifically,when the message ID is 0x8000 to 0x8004, the message ID can indicatethat the signaling message is an application signaling message. In aspecific embodiment, when a trigger included in the applicationsignaling message signals the position of triggering applicationinformation, the message ID may be 0x8000. When the trigger included inthe application signaling message signals an application lifecycle, themessage ID may be 0x8001. When the trigger included in the applicationsignaling message signals an application action, the message ID may be0x8002. When the trigger included in the application signaling messagesignals a content media time, the message ID may be 0x8003. When thetrigger included in the application signaling message includes alltrigger information, the message ID may be 0x8004. Since the message IDof the signaling message indicates the type of a trigger included in theapplication signaling message, the application signaling table may notinclude the trigger type information. In the embodiment of FIG. 39, theapplication signaling table does not include the trigger typeinformation differently from the aforementioned application signalingtable.

When the message ID identifying the application signaling message is setdepending on the type of a trigger included in the signaling message, asdescribed above, the broadcast reception device 100 can recognize atrigger type without parsing the application signaling table included inthe application signaling message. Accordingly, the broadcast receptiondevice 100 can selectively receive a specific type of triggerefficiently.

The broadcast transmission device 10 can transmit the applicationsignaling information through a generic packet. This will be describedwith reference to the following figure.

FIG. 40 shows a structure of an MMTP packet according to anotherembodiment of the present invention.

First of all, the syntax of the MMTP packet will be described.

The MMTP packet may include version information indicating the versionof the MMTP protocol. In a specific embodiment, the version informationmay be referred to as V. In a specific embodiment, the versioninformation may be a 2-bit field.

The MMTP packet may include packet counter flag information indicatingpresence of packet counting information. In a specific embodiment, thepacket counter flag information may be referred to as C. In a specificembodiment, the packet counter flag information may be a 1-bit field.

The MMTP packet may include FEC type information indicating a scheme ofan FEC algorithm for preventing errors in the MMTP packet. In a specificembodiment, the FEC type information may be referred to as FEC. In aspecific embodiment, the FEC type information may be a 2-bit field.

The MMTP packet may include extension flag information indicatingpresence of header extension information. In a specific embodiment, theextension flag information may be referred to as X. In a specificembodiment, the extension flag information may be a 1-bit field.

The MMTP packet may include RAP (Random Access Point) flag informationindicating whether an RAP for data random access of a payload isincluded. In a specific embodiment, the RAP flag information may bereferred to as R. In a specific embodiment, the RAP flag information maybe a 1-bit field.

The MMTP packet may include type information indicating a data type ofthe payload. In a specific embodiment, the type information may bereferred to as type. In a specific embodiment, the type information maybe a 6-bit field.

The MMTP packet may include packet ID information indicating an IDidentifying the packet. The broadcast reception device 100 can determinean asset including the corresponding packet on the basis of the packetID information. Further, the broadcast reception device 100 can acquirea relationship between the asset and the packet ID from the signalingmessage. The packet Id information may have a unique value for thelifetime of the corresponding transport session. In a specificembodiment, the packet ID information may be referred to as packet_id.In a specific embodiment, the packet ID information may be a 16-bitfield.

The MMTP packet may include packet sequence number informationindicating a packet sequence number. In a specific embodiment, thepacket sequence number information may be referred to aspacket_sequence_number. In a specific embodiment, the packet sequencenumber information may be a 32-bit field.

The MMTP packet may include timestamp information that specifies a timeinstance value of MMTP packet transmission. The timestamp informationmay be based on a UTC value. Further, the timestamp information mayrepresent a time when the first byte of the MMTP packet is transmitted.In a specific embodiment, the timestamp information may be referred toas timestamp. In a specific embodiment, the timestamp information may bea 32-bit field.

The MMTP packet may include packet counting information indicating acount of transmitted packets. In a specific embodiment, the packetcounting information may be referred to as packet_counter. In a specificembodiment, the packet counting information may be a 32-bit field.

The MMTP packet may include FEC information which is necessary accordingto an FEC protection algorithm. In a specific embodiment, the FECinformation may be referred to as Source_FEC_payload_ID. In a specificembodiment, the packet counting information may be a 32-bit field.

The MMTP packet may include reserved header extension information forlater header extension. In a specific embodiment, the header extensioninformation may be referred to as header_extension.

The broadcast transmission device 10 can insert application signalinginformation into a generic type packet. Specifically, the broadcasttransmission device 10 can insert the application signaling informationinto a payload of the generic type packet in the form of a file andtransmit the application signaling information. Here, the broadcasttransmission device 10 can allocate different packet IDs to files. Thebroadcast reception device 100 can extract the application signalinginformation from the generic packet. Specifically, the broadcastreception device 100 can extract a file including the applicationsignaling information from the generic packet. Specifically, thebroadcast reception device 100 can extract the file including theapplication signaling information on the basis of the packet ID of thegeneric packet. For example, the broadcast reception device 100 candetermine whether the packet includes necessary application signalinginformation on the basis of the packet ID of the generic packet.

The broadcast transmission device 10 may transmit the applicationsignaling information using the header extension information of the MMTPpacket. This will be described with reference to the following figure.

FIG. 41 shows a structure of an MMTP packet and a syntax of a headerextension field for application signaling information transmissionaccording to another embodiment of the present invention.

The broadcast transmission device 10 may insert the applicationsignaling information into the header of the MMTP packet and transmitthe same. Specifically, the broadcast transmission device 10 may insertthe application signaling information into the header extensioninformation and transmit the same.

In a specific embodiment, the header extension information may includeheader extension type information indicating the type of headerextension information included therein. Here, the header extension typemay indicate that the header extension information includes anapplication signaling message. In another specific embodiment, theheader extension type information may indicate the type of applicationsignaling information included in the header extension information.Here, the type of application signaling information may include atrigger type depending on the aforementioned trigger property. In aspecific embodiment, the header extension type information may bereferred to as type.

In a specific embodiment, the header extension information may be a16-bit field. In a specific embodiment, the header extension informationmay include header extension length information indicating the length ofthe header extension information. Here, the header extension lengthinformation may indicate the length of the application signalinginformation included in the header extension information. In a specificembodiment, the header extension length information may be referred toas length. In a specific embodiment, the header extension informationmay be a 16-bit field.

In a specific embodiment, the header extension information may include aheader extension value indicating extension information includedtherein. Here, the header extension value may represent applicationsignaling information included in the header extension information.Here, the application signaling information may be a trigger. Further,the type of the application signaling information may be a URI in astring form. The URI in a string form may be the aforementioned stringtype trigger. In a specific embodiment, the header extension value maybe referred to as header_extension_value.

Accordingly, the broadcast reception device 100 can extract theapplication signaling information from the header extension information.Specifically, the broadcast reception device 100 can extract theapplication signaling information on the basis of the header extensiontype information included in the header extension information.Specifically, the broadcast reception device 100 can determine whetherthe header extension information includes the application signalinginformation on the basis of the header extension type information. Thebroadcast reception device 100 can extract the application signalinginformation when the header extension information includes theapplication signaling information. Further, the broadcast receptiondevice 100 can determine the type of the application signalinginformation included in the header extension information on the basis ofthe header extension type information. Accordingly, the broadcastreception device 10 can selectively acquire the application signalinginformation.

Description will be given of operations of the broadcast transmissiondevice 10 and the broadcast reception device 100 according totransmission and reception of application signaling information inaccordance with the above-described embodiments of the present inventionwith reference to the following figures.

FIG. 42 shows part of a broadcast system according to an embodiment ofthe present invention.

In a future hybrid broadcast system, an interactive application relatedto broadcast programs may be delivered through a broadcast network orthe Internet and provided to users. To deliver the interactiveapplication to a receiver, a service worker, one type of web workers ofHTML5 which can be generally used in a browser environment, may be used.

The service worker may automatically store content items related to theinteractive application in a storage of the receiver depending oncharacteristics of type of the interactive application. Otherwise, thecontent items related to the application may be stored in the receiverby a user.

The receiver can provide a mechanism that can operate similarly to apackage application or a widget through the service worker and can driveapplications even in an offline state such as an Internet-disconnectedstate.

An embodiment of the present invention relates to a method of installingthe interactive application in the receiver through the service workerand/or interworking with addLink( ) API to provide applicationmanagement functions such as execution, termination, update and/ordeletion of the interactive application when a user wants.

The broadcast system according to an embodiment of the present inventionincludes a receiver J104100, a content provider/broadcaster J104200and/or an application service server J104300.

The receiver J104100 may include a signaling parser J104110, anapplication manager J104120, an application browser (or an applicationprocessor) J104130, a service worker J104132, a (non-real-time) NRTcontent manager J104140 and/or a storage J104150.

The signaling parser J104110 is a device or a module for parsing asignal sent from the content provider/broadcaster. The signal mayinclude signaling information (or signaling data) and/or content. Thesignaling information including application related information isacquired. The signaling information may include command information foridentifying a command related to application execution.

The application manager J104120 is a device or a module for managing anapplication when the application is present after the signal is parsed.The application manager J104120 generates a control signal with respectto an application action using information included in the signalinginformation.

The application browser (or application processor) J104130 is a deviceor a module for performing a process for executing an application. Theapplication browser J104130 processes the application according to acontrol signal. The application browser J104130 can perform interactivecommunication between the receiver and a server (or broadcaster), whichis necessary for a procedure through which the application is providedto a user.

The service worker J104132 may be included in the application browser orincluded as a separate device in the receiver. The service workerJ104132 is a module or a device for managing downloading of NRT contentor application related information from a server provided by the contentprovider/broadcaster.

The NRT content manager J104140 is a module or a device for managingnon-real-time (NRT) content. The NRT content manger J104140 processesNRT content transmitted in non real time.

The storage J104150 is a device storing data. The storage used in thepresent invention may include an internal storage of the receiver, acache in a browser for driving the interactive application and/or anexternal storage (e.g., external USB storage) connected to the receiver.The storage J104150 provides applications and/or signaling informationstored therein to the service worker J104132 or the application browserJ104130. The storage J104150 can receive and store an applicationthrough interactive communication with the application service server.

The application used in the present invention may correspond to anapplication provided by the content provider/broadcaster. Theapplication may provide an independent service or may be combined withbroadcast content to provide a service with higher quality to users. Theapplication can operate by activating (or launching), suspending,resuming or terminating (or exiting) actions.

The content provider/broadcaster J104200 provides content in thebroadcast system. The content provider/broadcaster J104200 can deliversignaling information related to the application to the receiver. Thecontent provider/broadcaster J104200 can transmit signaling informationand/or NRT content to the receiver through an NRT transmission network.The NRT content may include broadcast content and/or the application.

The application service server J104300 is a server providing datarelated to the application.

FIG. 43 shows an example in which a storage is included in the broadcastsystem according to an embodiment of the present invention.

The storage may be included in the broadcast system as an internalstorage J105100, a cache memory J105200 and/or an external storageJ105300.

The internal storage J105100 may correspond to a storage device includedin the receiver.

The cache memory J105200 may correspond to a storage device included inthe application browser.

The external storage J105300 may be a storage device outside thereceiver and may correspond to a general external storage device, aserver or a cloud storage. When the external storage J105300 correspondsto the server or cloud storage, the receiver and the external storageare connected through networking and the receiver can rapidly receivedata about an application at the request of a receiver user.

FIG. 44 shows operation of the service worker according to an embodimentof the present invention.

The service worker, a web worker of HTML5, can be driven by theapplication browser that can execute an application in the receiver. Theservice worker may be created to be activated when an initialapplication is executed or when a user wants. The service worker may bepositioned between the application server and a web application executedin the receiver to serve as a proxy for a network request transmitted tothe application server. When the service worker is activated, theservice worker processes a request for application content items whenthe application executed in the receiver sends the request to theapplication server. The service worker can receive and/or process aresponse from the application server.

The application content items may refer to the application or subsidiarycontent necessary to present the application.

FIG. 45 shows operation of the service worker in an offline stateaccording to an embodiment of the present invention.

The advantage of the service worker as a proxy role is that the serviceworker can store all or some application content items on theapplication server in a cache.

The cache can be used differently from a cache generally used in abrowser, and the cache defined in the service worker can be completelymanually controlled.

As shown, the receiver can execute an application even when the receiveris not connected to the Internet using application content itemsdownloaded from the application server and stored in the cache by theservice worker. In this case, the application browser can deliver arequest for the application content items to the service worker and theservice worker can check whether application content items suitable forthe request are present in the cache and deliver corresponding data tothe application browser.

FIG. 46 shows an application program interface (API) and metadata usedfor a receiver to execute an application according to an embodiment ofthe present invention.

As described above, the interactive application can be installed in thereceiver and provided to a user. When application content items for theinteractive application in a web application form are stored in adatabase (DB) (or a storage) or a cache by the service worker, thereceiver can execute the interactive application like a widget even inan offline state (i.e., the Internet is not connected). The interactiveapplication can call addLink( ) API of the application manager of thereceiver. Here, the application manger provides metadata related to theapplication to the application browser or the service worker such thatthe receiver can configure a page or a menu for a link.

When the user is viewing a program through the receiver, applicationnotification indicating presence of the interactive application relatedto the program may be displayed on the screen. The user inputs a commandfor executing the application to the receiver. The service worker in thereceiver may be registered or may register the application or the usercommand. An install button may be displayed during execution of theapplication and the user may install the application by selecting theinstall button. The service worker may control application content itemsto be downloaded and stored in a storage (an internal storage, anexternal storage or a cache). An application registration procedure ofthe service worker may include application installation and/orapplication activation. The application may call addLink( ) API of theapplication manager of the receiver. When the addLink( ) API is called,related metadata may be delivered to the application manager of thereceiver such that the application manager can configure an applicationwidget page. The application manager of the receiver may configure anapplication collection page and/or menu using the delivered metadata.Users may order operations of executing, terminating, updating and/ordeleting installed applications using the application collection page ormenu. When a user executes an installed application, the user may callthe URL of the application. When application content items correspondingto the URL are stored in the storage, the service worker may load theapplication content items from the storage.

The URL of the interactive application in a web application form may bestored in the receiver. The interactive application calls the addLink( )API of the application manage of the receiver, and metadata related tothe application may be delivered to the application manger such that thereceiver can configure a page or a menu for a link.

When a user is viewing a program through the receiver, applicationnotification indicating presence of the interactive application relatedto the program may be displayed on the screen. The user inputs a commandfor executing the application to the receiver. The service worker maynot be registered. In this case, the service worker may not downloadapplication content items which will be used in an offline state. Theinstall button may be displayed during execution of the application andthe user may input a command for selecting the install button to thereceiver. The application may call the addLink( ) API of the applicationmanager. When the addLink( ) API is called, related metadata may bedelivered from the application such that the application manager of thereceiver can configure an application link page. The application managerof the receiver may configure an application collection page or menuusing the delivered metadata. Users may input a command for executing,terminating, updating and/or deleting installed applications to thereceiver. A user may control link to the URL of an installed applicationto be executed to load application content items.

Table (a) of the figure shows an embodiment of addLink( ) API of theapplication manager. When the addLink( ) API is successfully called, thereceiver adds a link to a list of links. The integer returns a valueindicating whether the API has been successfully called and, whencalling fails, returns a value indicating the reason of failure. TheaddLink( ) may be called application link information. The applicationlink information includes a link and/or application property informationnecessary to execute an application.

The addLink( ) may include URI information and/or linkmetadatainformation.

The URI information indicates a URI value of a URL stored as a link. TheURI information may indicate a URL stored as a link for an application.

The linkmetadata information includes metadata related to a link. Thelinkmetadata information will be described in detail below.

Table (b) of the figure shows values returned by the addLink( ) APO anddefinition thereof. When “0” is returned, this value indicatessuccessful calling and addition of a link. When “1” is returned, thisvalue indicates that calling fails because the syntax of URI informationis not valid. When “2” is returned, this value indicates that callingfails because the linkmetadata information is not valid. When “3” isreturned, this value indicates that calling fails because the number ofstored links exceeds a permitted limit.

Table (c) of the figure shows a schema table of the linkmetadatainformation. The linkmetadata information may include @url information,@title information, @majChanNum information, @minChanNum information,@channelName information, @programName information, @expirationinformation, @packagedApp information, @description information, a Paramelement, @title information, @description information, an Icon element,@source information, @width information and/or @height information.

The @url information indicates a URL related to a link. The @urlinformation may represent the URL of an object indicated by a link.

The @title information indicates a link title displayed to a user.

The @majChanNum information indicates a major channel number of avirtual channel for which a link is provided. When the link is providedthrough an NRT service, this information can indicate some values (e.g.,upper 8 bits) of service_id information of the NRT service included in aservice map table (SMT).

The @minChanNum information indicates a minor channel number of avirtual channel for which a link is provided. When the link is providedthrough an NRT service, this information can indicate some values (e.g.,lower 8 bits) of service_id information of the NRT service included inthe service map table (SMT).

The @channelName information indicates a short_name of a virtual channelfor which a link is provided. When the link is provided through an NRTservice, this information can indicate the same information asshort_service_name information of the NRT service included in theservice map table (SMT).

The @programName information indicates title_text (a title representedby characters) of a program (e.g., a PSIP event, a broadcast program, abroadcast event or an event in an application) for which a link isprovided.

The @expiration information indicates an expiration date at which a linkbecome invalid.

The @packagedApp information indicates whether a linked URL correspondsto a widget or a packaged application. The receiver can recognizewhether the linked URL is a link for acquiring an application or awidget using this information. When the receiver is not connected to theInternet and the linked URL corresponds to the link for acquiring anapplication, application management such that shading may be performedsuch that the application cannot be executed.

The @description information indicates description about an application.

The Param element may be used to indicate a query string following a URLfor a link to an application. For example, in a URL ofhttp(s)://app.example.com/index.html?type=value, “type=value” maycorrespond to the Param element. For example, applications may bediscriminated by Param element values although they use the same URL.The application manager of the receiver may use the Param element togroup or search for applications associated with the same broadcaster orthe same program. A broadcaster or a content provider can efficientlymanage applications by discriminating the applications using Paramelement values without assigning different URLs to the applications.

The @title information indicates a title for the Param element.

The @description information indicates description about the Paramelement.

The Icon element identifies an icon file used to indicate a link in adisplay of links to a user. A plurality of icon files may be present.For example, icon files having different sizes or indicating the samelink may be present. One of such icon files may be displayed accordingto situation.

The @source information indicates a URL of an image file for an iconindicated by the Icon element.

The @width information indicates the width of an icon image in pixelunits.

The @height information indicates the height of an icon image in pixelunits.

FIG. 47 shows a user interface (UI) with respect to an application or alink for an application according to an embodiment of the presentinvention.

The receiver may provide a UI through which a user can select a desiredapplication or a link providing the application.

The aforementioned information included in the addLink( ) may be usedwhen the receiver provides the UI. For example, the receiver can displayan icon for an application or a link for the application using the Iconelement, @source information, @width information and/or @heightinformation. The receiver can display a title of an application or alink for the application using the @title information. The receiver candisplay information describing an application or a link in the UI usingthe @description information.

FIG. 48 shows a process through which a receiver installs and executesan application in the form of a widget according to an embodiment of thepresent invention.

An application in the form of a widget may be installed and executedusing the service worker and the addLink( ) API.

When the URL of an interactive application ishttp(s)://app.example.com/index.html, there may be multiple links (orURLs) for application content items included in the application, asshown.

The receiver may receive signaling information related to theapplication. The receiver may deliver the signaling information relatedto the application to the application manager (step 1).

The application manger may acquire the URL of the application includedin the signaling information and execute the application (step 2).

After execution of the application URL, application content items may bedownloaded through a broadcast network and/or the Internet when theservice worker is registered automatically or by a user (step 3).

The service worker may store the application content items in a storage(internal storage/browser cache/external storage) after downloading theapplication content items (step 4).

The application (or application browser) may call addLink( ) and delivermetadata related to the link of the application to the applicationmanger (step 5).

The application manager may store the delivered metadata in the storage(internal storage/browser cache/external storage) (step 6).

FIG. 49 shows a process through which a user executes an applicationupon installation of the application according to an embodiment of thepresent invention.

The URL of the application may be http(s)://app.example.com/index.htmland URLs or links of application content items may be as shown in thefigure.

A user may input a command for executing the application to the receiverthrough an installed app menu in the receiver. The installed app menumay be implemented in the form of a UI using metadata included inaddLink( ), as described above (step 1).

The application manger may execute the application URL. The applicationmanager may execute the application indicated by the URL. When the userselect a specific application, the application manger may be configuredto acquire the URL corresponding to the selected application and toexecute the application corresponding to the URL (step 2).

In a process through which the application or browser loads theapplication URL, the service worker is driven to load applicationcontent items stored in the storage. Since all application content itemsfor application execution are stored in the storage, the receiver cannormally operate the application even when the receiver is not connectedto the Internet.

As described above, according to the embodiments of the presentinvention, the broadcast receiver can correctly execute a desiredapplication of a viewer at an appropriate time even when the broadcastreceiver is not connected to the Internet or does not receive datarelated to the application through the current broadcast network, inapplication execution in the broadcast receiver.

FIG. 50 is a flowchart illustrating a method of executing an applicationby a broadcast receiver according to an embodiment of the presentinvention.

The broadcast receiver receives application signaling informationincluding information about an application (JS112010). The applicationsignaling information may be included in a broadcast signal andtransmitted, and the broadcast receiver may parse the applicationsignaling information from the broadcast signal.

The broadcast receiver parses application URL information including aURL at which a specific application can be acquired from the applicationsignaling information (HS112020).

The broadcast receiver receives one or more application content itemsrelated to the application identified by the application URL (JS112030).

The broadcast receiver stores the received application content items(JS112040).

All or some technical features described above may be added to each stepof the method of executing an application by the broadcast receiveraccording to an embodiment of the present invention.

The module or unit may be one or more processors designed to execute aseries of execution steps stored in the memory (or the storage unit).Each step described in the above-mentioned embodiments may beimplemented by hardware and/or processors. Each module, each block,and/or each unit described in the above-mentioned embodiments may berealized by hardware or processor. In addition, the above-mentionedmethods of the present invention may be realized by codes written inrecoding media configured to be read by a processor so that the codesmay be read by the processor supplied from the apparatus.

Although the description of the present invention is explained withreference to each of the accompanying drawings for clarity, it ispossible to design new embodiment(s) by merging the embodiments shown inthe accompanying drawings with each other. And, if a recording mediumreadable by a computer, in which programs for executing the embodimentsmentioned in the foregoing description are recorded, is designed innecessity of those skilled in the art, it may belong to the scope of theappended claims and their equivalents.

An apparatus and method according to the present invention may benon-limited by the configurations and methods of the embodimentsmentioned in the foregoing description. And, the embodiments mentionedin the foregoing description may be configured in a manner of beingselectively combined with one another entirely or in part to enablevarious modifications.

In addition, a method according to the present invention may beimplemented with processor-readable codes in a processor-readablerecording medium provided to a network device. The processor-readablemedium may include all kinds of recording devices capable of storingdata readable by a processor. The processor-readable medium may includeone of ROM, RAM, CD-ROM, magnetic tapes, floppy discs, optical datastorage devices, and the like for example and also include such acarrier-wave type implementation as a transmission via Internet.Furthermore, as the processor-readable recording medium is distributedto a computer system connected via network, processor-readable codes maybe saved and executed according to a distributive system.

It will be appreciated by those skilled in the art that variousmodifications and variations may be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

Both the product invention and the process invention are described inthe specification and the description of both inventions may besupplementarily applied as needed.

It will be appreciated by those skilled in the art that variousmodifications and variations may be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both of the apparatus and method inventions may becomplementarily applicable to each other.

Mode for Invention

Various embodiments have been described in the best mode for carryingout the invention.

INDUSTRIAL APPLICABILITY

The present invention is available in a series of broadcast signalprovision fields.

It will be apparent to those skilled in the art that variousmodifications and variations may be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

What is claimed is:
 1. A broadcast receiver for processing data of abroadcaster application, the broadcast receiver comprising: a tunerconfigured to receive a broadcast signal including video data for abroadcast program and application signaling information, wherein theapplication signaling information includes a URL (Uniform ResourceLocator) of an entry page of the broadcaster application for providingan interactive service; a network interface configured to receive atleast one application content item; a cache configured to store the atleast one application content item; a display configured to displaynotification information for the broadcaster application with displayingthe video data for the broadcast program, the display further configuredto display a first option for executing the broadcaster application anddisplay a second option for installing the broadcaster application afterthe first option is selected by a remote controller; and a processorconfigured to launch the broadcaster application after the applicationsignaling information is received; wherein the processor is furtherconfigured to forward the URL to a module for processing HTML5 withinthe broadcast receiver, wherein the module for processing HTML5 loadsthe entry page of the broadcaster application from the URL, and the URLis used to point to an external internet server or to the cache withinthe broadcast receiver, and wherein the broadcaster application isdelivered based on ROUTE (Real Time Object Delivery over UnidirectionalTransport) or broadband.
 2. The broadcast receiver of claim 1, whereinthe display is further configured to display at least one icon for theinstalled broadcaster application, highlight the at least one icon withdisplaying description information for the installed broadcasterapplication when the at least one icon is selected by the remotecontroller.
 3. The broadcast receiver of claim 2, wherein shading isapplied to the at least one icon when an internet connection is unable.4. The broadcast receiver of claim 1, wherein the at least oneapplication content item is received from the external internet serveror the cache within the broadcast receiver based on an internetconnection.
 5. The broadcast receiver of claim 1, wherein the at leastone application content item is received from the external internetserver or the cache within the broadcast receiver based on theapplication signaling information.
 6. A method for processing data of abroadcaster application in a broadcast receiver, the method comprising:receiving a broadcast signal including video data for a broadcastprogram and application signaling information, wherein the applicationsignaling information includes a URL (Uniform Resource Locator) of anentry page of the broadcaster application for providing an interactiveservice; receiving at least one application content item; storing the atleast one application content item in a cache; displaying notificationinformation for the broadcaster application with displaying the videodata for the broadcast program; displaying a first option for executingthe broadcaster application; displaying a second option for installingthe broadcaster application after the first option is selected by aremote controller; and launching the broadcaster application after theapplication signaling information is received and forwarding the URL toa module for processing HTML5 within the broadcast receiver, wherein themodule for processing HTML5 loads the entry page of the broadcastapplication from the URL, wherein the URL is used to point to anexternal internet server to the cache within the broadcast receiver, andwherein the broadcaster application is delivered based on ROUTE (RealTime Object Delivery over Unidirectional Transport) or broadband.
 7. Themethod of claim 6, further comprising: displaying at least one icon forthe installed broadcaster application; and highlighting the at least oneicon with displaying description information for the installedbroadcaster application when the at least one icon is selected by theremote controller.
 8. The method of claim 7, wherein shading is appliedto the at least one icon when an internet connection is unable.
 9. Themethod of claim 6, wherein the at least one application content item isreceived from the external internet server or the cache within thebroadcast receiver based on an internet connection.
 10. The method ofclaim 6, wherein the at least one application content item is receivedfrom the external internet server or the cache within the broadcastreceiver based on the application signaling information.